[RELEASE] src2pkg-3.0 - create packages from source

[scsijon]

What was the output from 'src2pkg --setup'?

-------------------------------------------------------------------------
[1;36m Notice - [0;39mCreating src2pkg-helpers:
src2pkg uses a shared library and a few programs
when creating packages. For best compatibility,
these binaries will be compiled on your system.
They are then installed in a private directory.
When done, src2pkg is ready for use.

TEMP_DIR=/usr/src/src2pkg/builds/src2pkg-helpers
Starting build in 5 seconds
[1;34mUnpacking sources - [0;39m[1;32mOK[0;39m
[1;34mCreating libsentry - [0;39m[1;32mOK[0;39m
[1;34mCreating tar-1.13 - [0;39m[1;32mOK[0;39m
[1;34mCreating coreutils - [0;39m[1;32mOK[0;39m
[1;34mCreating unionfs-fuse - [0;39m[1;31mFailed! [0;39mError is non-fatal. Continuing...
[1;34mCreating pet package - [0;39m[1;32mDone [0;39m
[1;34mFinished pet package is:[0;39m
/usr/src/src2pkg/src2pkg-helpers/src2pkg-helpers-1.6-i486-1.pet
[1;34mInstalling pet package - [0;39m[1;31mFailed! [0;39m
Failed to install package: src2pkg-helpers-1.6-i486-1.pet
---------------------------------------------------------------------------------
Actually, looking and comparing with my 551, I think it's saying it's 'failing' for the unionfs package, which quirky April
doesn't use, it seems to install all the other files in the right src2pkg places, although the packages coreutils5.21b (8.22)
and tar1.13 (1.28 ) are older than April uses so don't know if that affects it also.

I shall have a go at a build and install with something simple this evening, (it's woodcutting season here at present) days are busy.

[amigo]

Yeah, unionfs-fuse is optional. The rest looks alright. Don't worry about the coreutils and tar version -these tools get installed in to a 'proprietary' path away from your system tools where they are available to src2pkg. It uses the old coreutils version because their behavior is known and uses old tar for creating slackware-compatible packages.

It does say that the final src2pkg-helpers package installation is failing, though. If true, you may need to manually install it -it should be under /usr/src/src2pkg/src2pkg-helpers. But you can check to see if it is already installed by running 'which src2pkg'.

[harii4]

Would src2pkg work with/on a raspberry pi (raspbian) ?
Or only on a full blown debian or puppy?

Might have to update to a newer puppy to use src2pkg-3.0 due to still using Tgz-pup.

[amigo]

src2pkg will work anywhere you have enough development tools installed.

[live]

Hi,

On tahrpup64 with its devx, what do I need to compile 64bits pet?
By default it builds i486 pets

into "etc/src2pkg/src2pkg.conf", I tried to modify

[[ $ARCH ]] || ARCH="m64"
[[ $MARCH_FLAG ]] || MARCH_FLAG="m64"

And ran

Code: Select all

src2pkg -CWD -PET --arch=m64 <source tar>

But it fails

Thanks

[amigo]

You need this in the conf file:

Code: Select all

[[ $ARCH ]] || ARCH="x86_64"

[s243a]

You need this in the conf file:

Code: Select all

[[ $ARCH ]] || ARCH="x86_64"

I haven't gone through this thread yet, but I presume that you would have to run the configure scripts before running this pet, in order to make sure that you have all the correct dependencies installed.

A good test for this package would be the ruby package since some environmental variables in ruby are hard coded at compile time.

The difficulty I had with making pets is that for some packages the compilation may depend on where you compile to, and this makes setting the prefix and then using dir2pet not a directly workable approach.

[live]

Thanks

[Keef]

src2pkg will run configure. You can use your own options with:

Code: Select all

src2pkg -e='--disable-something --with-summatelse' tarball-name

etc.

You can also create build-scripts with your options, so it is easily repeatable.

The documentation is well worth a read.

[scsijon]

sorry amigo but v3.0 is failing with barryk's latest quirky 8.1.6, just junk in output package and things like wrong directories's etc. Wonder if it's because it's working from /file and not /root.

regards

[scsijon]

Hi amigo, barryK's latest xerus 8.3 is out and I tried to install src2pkg, but it failed during the --setup phase saying it wanted gcc, which he doesn't use anymore (and most of us are going the same way).

Any possible chance of a new version as I do love your package for it's capabilities for building and testing things on the fly, even if their removed straight afterwards because their not what they were thought to be.

thanks
scsijon