Re: buildpkg - a new way to build packages

gapan · **Posted:** Mon Mar 30, 2009 8:04 pm

buildpkg 1.6.1 doesn't unzip .zip source files automatically any more... (only for me it seems)

maximus · **Joined:** Wed Oct 03, 2007 4:53 pm **Posts:** 264

You're not the only one.... :'(

Ejis · **Posted:** Wed Apr 08, 2009 6:21 am

Same problem.

_PN_boy · **Posted:** Wed Apr 08, 2009 6:37 am

Hi,

please apply the following patch.
This "bug" was introduced by a different mime-type, although this doesn't happen on any of my three systems, probably related to gnome mime-types?

Regards,

Shador · **Posted:** Tue Apr 21, 2009 12:30 pm

Now that apart from .tgz also .tlz, .tbz and .txz have been introduced, I think it would be a good choice give packagers the possibility to choose the package extension. That's all that needs to be done, just give makepkg another extension and with the appropriate software installed it will handle it properly.
It would also be a great feature to have the possibility to specify more than one extension, thus building several package formats at a time (/ one after the other).

maximus · **Joined:** Wed Oct 03, 2007 4:53 pm **Posts:** 264

Shador wrote:

Now that apart from .tgz also .tlz, .tbz and .txz have been introduced, I think it would be a good choice give packagers the possibility to choose the package extension.

I hope I'm not overstepping "the line" or anything (and apologies in advance if I am), but....
I attacked this particular problem by adding a compression type variable to ZENBUILD with the appropriate patch to buildpkg, giving users a choice between txz, tlz, tbz and tgz compression types.
The patch first checks that the variable $compression has been set in the ZENBUILD, then verifies that the extension used is a valid compression type. If both are true, the package ends up being compressed with the chosen compression algorithm.
I don't wish to step on anyone's toes or anything like that, I realize that if I can figure this out then there's almost certainly a better implementation that can be put in place by the buildpkg developer(s), I'm just dipping my toes into scripting and am excited that it works!

Edit: On second thoughts... we've used tgz on its own for a long time, would it be OK to just use txz for example? I also encountered a problem when using requiredbuilder with txz packages - I get "Package format not recognised" output to the generated depfile. Depfinder however does support txz.

_PN_boy · **Posted:** Mon Jan 11, 2010 8:23 am

New version: v1.7.0
CHANGELOG:
fix mimetypes for zip unpacking
added native support for txz and tgz. txz is now the default, tgz is an option -t or --tgz

Re: buildpkg - a new way to build packages

Who is online