On Wed, 19 Jun 2002, Zdenek Kabelac wrote: > > tarball, that is not a cvs snapshot, and has a sane name like > > "avifile-0.7.7.tar.gz" with the tarball unpacking in a dir like
Hm, well, I got the latest snapshot and it unpacked in a dir called avifile0.7-0.7.7 so yes, I wonder why that is. Also, I don't really understand what adding the date to the tarball name adds. IMO there's nothing wrong with just using the version numbers, it's a *lot* less confusing for users. Especially when the final dir contains the version number twice, and differently, and doesn't have the date. I don't see why a tarball should unpack in a different dir than the name suggests. So that's why I'm asking. > I doubt there will ever be plain x.y.z release with a date - I like > the date in the release number. Can't you make an exception just once in a while (like every three months or so) to make it easier on other projects ? This way they can agree to work against a semi-stable version for some time instead of all taking their own snapshots. > > various snapshots. It would be great if a semi-stable release could be > > made before 0.8.0 so that these projects can update against a temporarily > > I'm plannig to release 0.8 within few weeks.... Great ! > > stable release. If I can help in any way to make this happen, please let > > me know (ranging from help on build stuff, autotools to building clean > > packages in build roots). > > Well if you want to help with maintiaing releases you are > wellcome - however the building scripts should already be > quite clean - cvs snashots are build with make dist > and even make dist-check mostly works with avifile One thing that might be changed is, judging from what I see, is that all of the libs are linked to QT when qt is found. I guess qt is only needed for the actual apps, and thus it would be a lot better for people if the libs weren't linked to it. So maybe that could be split up. > I think far more usable would be to put there at least few > pages about documentation to help users with these problems > (as I think avifile as capable of many thing users simple don't know about > (and no other player has them as well...)) Probably, yes, but I don't know enough about avifile to be able to do that ;) I'm having a hard time as it is trying out applications that use avifile. I am thinking though about setting up a system that compiles these apps linked to their version of avifile and create wrappers for those apps to detect their custom version. That might be easier on end-users. Thomas -- The Dave/Dina Project : future TV today ! - http://davedina.apestaart.org/ <-*- -*-> Ooh child I'll meet you child On the sunny side it's alright <-*- [EMAIL PROTECTED] -*-> URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/ _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
