I know that there is slam64 but it's not a official port and for that i don't want to use it so please do not reffer to it
I know you've said don't refer to Slamd64, but, I feel I can't *not* refer to it when discussing x86_64 ports. In short, let me say that I don't believe there will be an x86_64 port for a very very long time yet.
In long, let me explain why ...
But first, let me say a few things for and against Slamd64. We'll use it as a case study, so to speak, and to highlight some of the good and bad it is.
* Pat helped slamd64 maintainer Fred build slamd64.
* Security updates from Slack -current equally get applied to Slamd64 -current.
* It is functional and functionally like Slack.
* It is being actively worked on.
* Busybox still has some problems with x86_64 hardware, so installation is only smooth in about 50% of cases (hardware dependant).
* Slack "stable" programs may not compile straight on to x86_64 due to the age of the software. What's stable in Slack 10 just plain doesn't work in Slamd64 (in some cases).
* Similar to above, the toolchain in Slack 10 is not as suitable for x86_64 as it is for i486, marking yet another discrepency between them.
x86_64 hardware (in my opinion) is still not as intrinsically stable as i386. Although it is getting better all the time (the development cycle appears rapid), ultimately the combination of "new" (yes, I know it's been around for a while - but not as long as x86!) consumer hardware and new software to run on that hardware gives it an intrinsic instability. My understanding of an "official" Slackware port is drawn from this paragraph:
The goal of the Slackware ports is to imitate the user experience of the Intel distribution as closely as possible. This means that the ports will attempt to include all of the same software, configuration scripts, and so forth.
As I've pointed out already, some packages in stable Slack just don't play nice when compiled for a x86_64 platform. Therefore, until Slackware stable catches up to newer toolchains and programs, you won't get an "official" port, because those packages *can't* be ported sensibly to provide a stable Slack-64.
A few disclaimer points:
* My figures are rough, please don't quote me.
* I have a tendancy to jump on any x86_64 thread. It's a topic that interests me, sorry =)
* If you haven't tried Slamd64, try it before you disregard it. Perseverance is the key - once you're past installation, the rest is plain-Slackware-sailing.
* I'm a Slackware advocate, and would love to have an "official" port, but Slamd64 is a good interim, or even starting point for that to occur. The more support they get, the better slamd64 becomes, the faster it becomes stable ...
- Piete "Oh thank goodness, he's finished" Sartain.