On Mon, Jun 29, 2009 at 16:10, Eric Hameleers <[email protected]> wrote:
> On Sun, 28 Jun 2009, Darrell Anderson wrote: > > When 13.0 is released, will the slackbuilds.org build scripts continue >> supporting the older tgz format, the newer txz format, or the option to use >> either? >> >> Thanks. >> >> P.S. I'm not a member of the list. >> >> Darrell Anderson >> http://humanreadable.nfshost.com/ >> > > It's really quite simple Darrell: > > We are a site that hosts SlackBuild scripts, not packages. It is not about > supporting any particular package format. If you want to use the old .tgz > packages, then by all means edit the last line of the script and change the > extension of the package which is going to be created. These scripts are not > set in concrete. > > When we start adding scripts for Slackware 13.0 in our repository, you can > expect that they will (or should) support *all* of Slackware 13.0's features > - which includes the new package formats. When we sign off a script after > our internal QA round we will have tested it on a full install of Slackware. > > Regards, Eric > > The problem becomes more clear when we know SBo only host scripts but not packages and people can edit them when they feel disappointed. My suggestion is add a FMT variable like this: FMT=${FMT:-tgz} ... /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$FMT So users don't need to modify the script to change the compression algorithm.(As local modifications will lost after every rsync...) -- Cheers, Grissiom
_______________________________________________ SlackBuilds-users mailing list [email protected] http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
