a flame war?? again ??? sorry guys, but this HAS to be included.. did you think about all the people using archs that doesn't have a packaging system, or their packaging system doesn't include tls (like ubuntu WAS), how about the users who just install using autopackage, or bitorck installer.. yes, we should include tls for those installers, but for everything else, dependencies.. we don't include tls because we're amsn, not tls, it's a different project.. yes, we need an X server to run amsn, are we including X in our package ??? same applies to tcl/tk. So no, we shouldn't include it in our package, BUT, did you see how many people have the tls problems ???? almost 95% of the people, I assure you!!! we want to make life easier for our users, not for us, or at least, find something in between. Yes, there is the dependencies, but then, how many distros had a wrong tls package ???? with a pkgIndex.tcl doing a load on [file join $dir .. libtls1.50.so] while the libtls1.50.so was in /usr/lib/tls1.50 not in /usr/lib/ ALOT.. really a lot of distros had a wrong tls package, so many users had it installd and not working, I spent a lot of time trying to make that work for them, trying to figure out if the pkgIndex.tcl is incorrect, if the libtls1.50.so is a wrong symlink, if it's in the wrong dir, etc.... YES, it is the tcltls packager's fault, not ours, but when it's his fault, it's OUR users that will not be able to use amsn and will switch to gaim or whatever, if they don't, they'll be asking us on how to make that work "it keeps telling me to install tcltls, but I have it installed".. and it's out time that we'll waste trying to help them. Why remove the damn downloader, it's already implemented damn it!!!!!!!!!!!!! anyways, I really think you should all stop trying to make it *standard*, and start thinking about the users and about the support team a little.
KaKaRoTo On Sat, 27 May 2006 11:56:16 -0400, Karol Krizka <[EMAIL PROTECTED]> wrote: > On Sat, 2006-27-05 at 02:03 -0400, Youness Alaoui wrote: >> ok, how about ubuntu (iirc) the package didn't work because 'tcltls' >> didn't exist in their repos... > Seems like the ubuntu problem has already been fixed for Draper Drake > release. > >> 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 >> ? > I don't think that should be a problem. If you are compiling from source > instead of using a premade package if availible, then you better know > what you are doing and that you need to install requirements yourself. > >> >> 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) >> > Why didn't we include it with aMSN core in the first place? Wasn't there > a licensing issue or something? > > -- > Cheers, > Karol Krizka > > > > _______________________________________________ > 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
