Humm.. thanks for noticing.. we'll have to put it again in a different filename to avoid the problems with had with the mirrors when 0.95 was released... About autopackage, here is a discussion I just had in the channel.. in short, let's give ONLY Autopackage for download... keep a link, not too easy to find, that would say 'hey, if you're a native package system religious kind of person, click here to access your distro's specific package" where we'll put the packages you guys did (too stupid to waste that effort...) Someone will also have to set up a poll in the webpage asking about the autopackage, I don't know much about the questions we could put but here are some ideas : What do you think about the linux packages aMSN provides : 1 - I use windows/mac so I don't care 2 - All I want is for it to work, no matter which package I use 3 - I really like autopackage and would want to use it 4 -I'm too religious about my native distribution's packaging system, so I don't want to use anything else by my distro's specific package 5 - no opinion/don't care
Now, here's the log : <KaKaRoTo-KS> I have one more small question.. how easy would it be to create an empty rpm/deb with the autopackage embedded, which will extract the autopackage to a temp dir and with a pre-install script that launches the autopackage binary, and a pre-uninstall script that launchs 'package remove' ? <KaKaRoTo-KS> (is it even possible ? I don't know much about packaging...) --- TD[gone] is now known as TD <TD> KaKaRoTo-KS: i guess you could do <TD> KaKaRoTo-KS: but it begs the question - why? <KaKaRoTo-KS> TD: the reason why is simple : we want to have only one package (AP) but I'm sure most of our users will want to use their default distro's packaging system instead of having an additional packaging system... <TD> wrapping it in an rpm won't solve that <KaKaRoTo-KS> We're tired of having around 10 packages (and our release has been delayed for several weeks so we can get our hands on all the packages we need before officialising the next release) so we thought it might be best to have only one generic RPM and one generic DEB <TD> ultimately autopackage exists because the distros native packaging systems aren't good enough .... <TD> yeah well that's how some projects do it <TD> actually it seems most users don't mind having an extra package type on their system <TD> it's not been an issue for inkscape, for example <TD> you might get a few who are religious about it <KaKaRoTo-KS> problem is that it's not easy to have generic rpms/debs so we thought about using AP core to detect where to put desktop files, etc... <KaKaRoTo-KS> ok <KaKaRoTo-KS> you really think 'a few' will be religious about it ? <KaKaRoTo-KS> I would think a lot of people would be.. <KaKaRoTo-KS> we have a userbase of around 1 million users (mac/windows users included) <KaKaRoTo-KS> and I really think people will start complaining <KaKaRoTo-KS> I'm ready to take the risk, release the RC1 of our next version with AP only and see what it gives us <KaKaRoTo-KS> but for one, I would prefer to use my native packaging system :) <TD> well, i can only go from experience <KaKaRoTo-KS> yeah, good point <TD> probably depends partly on what the program is. most of inkscapes users are arty types who don't get that religious about stuff like packaging <TD> they just want it to work, in other words <KaKaRoTo-KS> and if the experience says that 50% (an example) of our users will refuse to install the product because they don't find their distro's rpm/deb ? are you thinking about a solution ? <KaKaRoTo-KS> humm.. well, our users also would only want it to work... the project is aMSN, a multiplatform MSN messenger client <KaKaRoTo-KS> instant messenging.. mostly depends on tcl/tk <KaKaRoTo-KS> no other lib* dependency.. <TD> ah ok <TD> i thought you already had an autopackage? <TD> i suspect most people won't install if they don't see a distro specific RPM/DEB because they've learned the hard way it won't work otherwise <TD> eg installing a mandrake rpm on red hat won't necessarily work <TD> and as the alternative of handling source code is hard/painful ..... --> pauluk ([EMAIL PROTECTED]) has joined #autopackage <KaKaRoTo-KS> yes, we do have an autopackage, but we also have other packages.. we'd want to minimize the number of packages we have, that's the aim <KaKaRoTo-KS> http://sourceforge.net/project/showfiles.php?group_id=54091&package_id=48692&release_id=37621 <KaKaRoTo-KS> here are all our packages and the number of downloads of each <KaKaRoTo-KS> seems AP is not 'ignored'... it has been downloaded several times indeed <KaKaRoTo-KS> TD: Thanks for the help <TD> sorry <TD> am in 3 conversations at once <KaKaRoTo-KS> I'll tell the others to try providing the AP package only and see the results.. I'll also set up a poll in our website to see what users think <KaKaRoTo-KS> nah, don't worry, I know what it means to give support :) <TD> right, ok, will be an interesting experiment <KaKaRoTo-KS> you've been helpfull already <TD> if people want RPMs of course they can also be contributed <TD> or you can just say "well send them to your distro repository" <KaKaRoTo-KS> yes <TD> a few people will complain but most users never post to anything <KaKaRoTo-KS> I wanted a rpm/deb that would be generic for all distros because it has autopackage embeded in it <KaKaRoTo-KS> this way all of your hard work will be used to determine what to install where, etc.. <KaKaRoTo-KS> but people will still don't see it (so won't complain :)) <KaKaRoTo-KS> if the experiment turns out bad, we'll try to do that <TD> heh <TD> well i think they'd notice .... <TD> ok <TD> i shall follow it with interest <KaKaRoTo-KS> they'd notice but they won't yell (purpose: not please the users, just prevent them from asking questions and wastnig our time by giving useless support :P) KKRT On Fri, Jul 07, 2006 at 03:43:37PM +0200, Philippe Valembois - Phil wrote: > Le Friday 07 July 2006 12:40, Vivia Nikolaidou a ?crit?: > > On Thu, 6 Jul 2006, Youness Alaoui wrote: > > > WHEN IS THE 0.96 GONNA BE RELEASED... AT LEAST RC1.. damn it... RC1 is > > > so outdated now, I wonder if it's worth it to release it now... here's > > > what I think, release the nsis installer for windows (yeah, we might > > > drop bitrock completly, nsis is much more advanced, maybe once bitrock > > > becomes more mature, we'll use it...) and the autopackage for linux, and > > > forget about the other binaries, maybe create a full list of packages > > > for the final 0.96 release, but for RC1, let's have an autopackage and > > > STOP WASTING TIME!!!!!!!!!!! > > > Hum... There was a trouble with the tar.gz : it was corrupted so all mirrors > are wrong with it... > The tar.bz2 is good... > I am doing FC4 RPM > And it will just miss DMG and ebuild to release... > Phil > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
