Haha, good to know this nowgapan wrote:You don't have to. Just don't provide a new dep file with the new version and the renaming will happen "on the fly" in the repository. metagen.sh does that already.thenktor wrote:But I don't want to rename my dep files manually everytime i build a new package Why not keep the 'keepdepfile' feature?
slkbuild (formerly buildpkg) features
Re: buildpkg features
Re: buildpkg features
OK, here's my "buildslackpkg"...
http://pnboy.pinguix.com/gapan/buildsla ... ch-1gv.txz
No more ZENBUILDs, it's SLKBUILDs now... No dependency support whatsoever, no more zenver and added support for tgz, tlz and tbz packages in SLKPKG options (default is txz).
http://pnboy.pinguix.com/gapan/buildsla ... ch-1gv.txz
No more ZENBUILDs, it's SLKBUILDs now... No dependency support whatsoever, no more zenver and added support for tgz, tlz and tbz packages in SLKPKG options (default is txz).
Re: buildpkg features
perhaps we can define packaging rules now, so that we can start working on building packages as soon as we get time.
by the way, the buildpkg still generates ZENBUILD template!
by the way, the buildpkg still generates ZENBUILD template!
'Tommorow is like today, just happens tomorrow.'
Re: buildpkg features
I'd say: Same as Zenwalk!tsuren wrote:perhaps we can define packaging rules now
Re: buildpkg features
Why not just slkbuild as package and binary name? Based on the model of pkgbuild and according to the filenames it parses (SLKBUILD).gapan wrote:OK, here's my "buildslackpkg"...
No more ZENBUILDs, it's SLKBUILDs now...
buildslackpkg is a bit long Furthermore I think it's easier to understand for newcomers that the slkbuild tool parses the SLKBUILD file.
Re: buildpkg features
You're right.thenktor wrote:Why not just slkbuild as package and binary name? Based on the model of pkgbuild and according to the filenames it parses (SLKBUILD).
buildslackpkg is a bit long Furthermore I think it's easier to understand for newcomers that the slkbuild tool parses the SLKBUILD file.
I'll make the change this afternoon.
Re: buildpkg features
Yes.thenktor wrote:I'd say: Same as Zenwalk!tsuren wrote:perhaps we can define packaging rules now
Lets just only change the package versioning in slackware fashion. Instead of:
$pkgname-$pkgver-$arch-$zenver.$pkgrel.txz
we use
$pkgname-$pkgver-$arch-$pkgrelxy.txz
where xy are your initials. When we come up with a name, maybe we can put initials for that there instead.
Re: buildpkg features
It's ok for me. I've always used this naming scheme for self compiled Slackware packages So my suffix would be "tm".gapan wrote:we use
$pkgname-$pkgver-$arch-$pkgrelxy.txz
where xy are your initials. When we come up with a name, maybe we can put initials for that there instead.
Re: slkbuild (formerly buildpkg) features
Tell me what you think:
http://pnboy.pinguix.com/gapan/slkbuild/
http://pnboy.pinguix.com/gapan/slkbuild/
Changelog:
- v0.1 (June 10, 2009)
* Initial release as slkbuild
* Creates txz packages by default
* Added option for creating tgz, tbz or tlz packages
* If sourcetemplate is not set, an src file will not be created
* Removed all dependency related stuff
* Removed zen-pkgcheck.pl option
* Removed automatic installation of .desktop files that appear in the source array
* Removed zenver variable, package name now is $pkgname-$pkgver-$arch-$pkgrel.txz
* Renamed ZENBUILD to SLKBUILD and buildpkg to slkbuild