ok, how about ubuntu (iirc) the package didn't work because 'tcltls'
didn't exist in their repos... and some people use the autopackage or
bitrock...
but yes, about SELinux, indeed, the dependancy should take care of that by
itself, but what if the FC user installed amsn by compiling from source ?
or using the bitrock installer ?
I think we should provide packages with and without tls and leave the
choice to the user (with a radio button like opera had in their website
for downloading opera with our without JVM), but for now, how the
packaging will be done is something, how the tls autodownload works is
something completely different, so let's just give all the possible
choices and let the user do it, if we're lucky, the autodownloader will
never be executed if everyone uses a good packaging system that resolves
depedencies.
KaKaRoTo
On Fri, 26 May 2006 16:59:59 -0400, Philippe Valembois - Phil
<[EMAIL PROTECTED]> wrote:
> Hi,
> I think we shouldn't provide packages for FC on the website....
> We will provide them trough the extras repository... With it, yum will
> download all dependencies... So if we need a new version of libc it will
> download it automatically....
> Phil
> P.S. Sorry to not being present since the beginning of the week... Many
> work
> at school (and not often at home since I had a car to go out....)
>
> Le Friday 26 May 2006 22:36, Sander Hoentjen a écrit :
>> The way I see it:
>> tls was as a seperate download because amsn was tcl/tk, so doing it this
>> way required no compiling.. Now we have parts in c, so we have to
>> compile anyway. What is the use of not including it?
>>
>> Sander
>>
>> On Fri, 2006-05-26 at 16:24 -0400, Youness Alaoui wrote:
>> > Well, tls has no problems with SELInux, right ?
>> > problem is in TkCximage.. so how about dynamic builds for the FC
>> distros,
>> > since those distros are the ones using SELinux..
>> > also have in the list of packages "your package didn't work, download
>> > this and read the INSTALL file"
>> > We should also change the message that's outputed when tkxmage is not
>> > found, now it says to read the INSTALL file, but the file doesn't
>> exist
>> > in distro packages.. so mabye change it into
>> > if { [file exists INSTALL] } {
>> > ...
>> > else
>> > error "Please download the source package from http://.. and
>> compile
>> > it." }
>> >
>> > KKRT
>> >
>> > On Fri, 26 May 2006 15:38:44 -0400, Vivia Nikolaidou
>> <[EMAIL PROTECTED]>
>> >
>> > wrote:
>> > > Good idea,
>> > >
>> > > btw, conclusion about SELinux and tls 1.5 ? We can:
>> > >
>> > > a) let SELinux users install Sander's RPM and offer the static build
>> > > instead
>> > > b) have two options: Linux (static build) and Linux (dynamic build)
>> or
>> > > something similar
>> > >
>> > > or... any better ideas?
>> > >
>> > > PS: am I slowly getting active again? :)
>> > >
>> > > On 5/26/06, Youness Alaoui <[EMAIL PROTECTED]> wrote:
>> > >> Hi there,
>> > >> as you probably know, the tls autodownloader isn't working for some
>> > >> time now because the URL for the download is to a mirror which is
>> not
>> > >> working anymore...
>> > >> So.. if we change the mirror, we might get the same problem some
>> other
>> > >> time, so how about we do this instead
>> > >> http://amsn.sf.net/download-tls.php?platform=win32
>> > >> and it will automatically choose a different mirror each time and
>> > >> redirect
>> > >> to it.
>> > >> in case this one fails (because SF web servers are down more often
>> > >> than sf
>> > >> file releases mirrors), then use a hardcoded URL for a mirror (or
>> > >> random between a few hardcoded ones).
>> > >> Advantage is that if we had done this in the first time, then we
>> > >> probably
>> > >> would have been able to make amsn users download tls 1.5 without
>> > >> releasing
>> > >> a new version nor having the users update their amsn version.
>> > >> What do you think? shall it be done ?
>> > >>
>> > >> --
>> > >> KaKaRoTo
>> > >>
>> > >>
>> > >> _______________________________________________
>> > >> Amsn-devel mailing list
>> > >> Amsn-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
>
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
KaKaRoTo
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
