On Fri, 02 Dec 2005 22:42:39 -0500, Karol Krizka <[EMAIL PROTECTED]> wrote:
On Tuesday 29 November 2005 08:31, Youness Alaoui wrote:
On Tue, 29 Nov 2005 10:52:37 -0500, Karol Krizka <[EMAIL PROTECTED]>
wrote:
> On Tuesday 29 November 2005 06:05, Youness Alaoui wrote:
>> who has 64 bits.. who can answer him ?
>
> What I did was just install the tls package from the gentoo portage.
You
> might
> want to search for "tls" in the Mandriva install thing.
well, the problem is that most people on the forums want to compile it
and
it doesn't work.. I don't know if that's our problem, but I just wanted
to
point out that we may need to add binary support for 64bits
architectures.
>> AND, do you think we should add a tls 1.5 download with the tls
>> auto-installer and tls for 64bits ?
>
> We could add tls as a dependency (an optional one?) to the RPM if it
gets
> installed through some automatic thing like apt or yum. I can also
> provide
> the 64bit binaries if we want an option for autoinstalled. Also do you
> want
> to update the rest of architectures to 1.5?
yep, I'd like to have the 64 bit binary in the auto-installer, since
more
people are using 64 bits archs, we can't just say "yeah, if you use
64bits, go compile it yourself" and also, it seems that tls 1.4 doesn't
work for 64 bit, you need 1.5 in order for it to be 'compatible' with
64bit.. so I don't want to have a list of 1.4 and 1.5 downloads, it
would
be better to have it consistent everywhere...
I have created the x86_64 binary and would like to add it to the list.
But
since we are downloading the packages from sf.net file release system
and I
don't have permission to use it, could someone else upload it? I can
email
you the package.
someone else can upload it for you, I can't right now, or you can put it
in the 'things to do when we do a release' wiki page, and add "update tls
packages"... so we update all of them.
can you post it to the wiki as an attached file until we put it in SF ?
(that is of course only if no other admin has the time to add the file to
the file releases...
And about updating the other architectures. Are there any volunteers to
do it
on it on their own computer or should I use the sf.net's compile farm?
you must ask for the compile farm and wait for SF.net to accept you (given
your reasons/motivations) before you can access the compile farm.. yeah, i
know.. it sucks...
can someone also confirm that 1.5 for x86 works with 64bit archs ?
http://sourceforge.net/project/showfiles.php?group_id=13248&package_id=2183
6 here are the releases of tls (official), I don't see as many options
as
amsn gives.. if I remember correctly we offer a lot of options, right ?
I
suggest we also keep it to a minimum, remove the windows/mac because
it's
already shipped with it, the only problem is source package for linux...
I'll remove Win and Mac when I add the x86_64 package.
will be done at the same time as update tls packages..
rpms and deb files (and autopackage and klik, and..) will all depend on
tcltls, so it's not a problem..
I also would like to suggest that we automatically install tls with
amsn,
instead of giving radio buttons and the choice to the user to select his
platform... using the ::tcl_platform we already know what's the
platform,
so why bother asking the user ??
Added to wiki.
Thanks
--
KaKaRoTo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
