ytoolshed / multipkg Goto Github PK

Multipkg.pm references a "confdir", which is supposed to contain a spec.template file and some other junk. All of this is missing from github. It'd be nice to have a semi-usable example of at least a spec.template, if not some of the other confdir stuff.

We should be able to query a .rpm or .deb package's metadata to determine info about how it was built.

I'm thinking at least:

• system info (uname -a output)
• cmdline and args run to build the package
• build system fqdn
• user
• revision control system specific information
  • p4 counter/git sha/svn-whatever at the time of build
  • branches/tags/etc that were specific to the build
• What else?

The goal is to make it simple to reproduce the package build given only the output package.

am i missing something, or is multipkg packaged with multipkg? there's no (clear) way to install it without already having a functioning copy.

I can't make the -N/--branch options work.

Reproduce with:

$ git-multipkg -b http://github.com/ytoolshed -N git-multipkg-build-from-branch-broken multipkg
$ rpm -qpl multipkg*rpm | grep THIS_SHOULD_EXIST
$ echo $?
1

You can see the file that I created in that branch here:

https://github.com/ytoolshed/multipkg/blob/git-multipkg-build-from-branch-broken/root/usr/bin/THIS_SHOULD_EXIST

If permissions on your ~/.cpan directory are incorrect, Seco::Multipkg::CPAN holds with no errors to STDOUT/STDERR.

I had to strace to figure out what was going on:

write(1, "WARNING: CPAN.pm is unable to write a configuration file. You\nmust be able to create and write to '/home/vagrant/.cpan/CPAN/MyConfig.pm'.\n\nAborting configuration.\n", 164) = 164

/home/vagrant/.cpan/CPAN/MyConfig.pm was owned by root and multipkg was running as user 'vagrant'

We should either use a temp .cpan directory or do proper perms checking on the default.

The generated DEBIAN/control file should contain an Installed-Size field that lists, in kB, the size of the package in uncompressed installed form. It's reasonable to calculate this based on du during the build process.

Additionally, the DEBIAN/md5sums file should contain checksums for each file (other than files that live in /etc/). The format is:

6aa8bbdec48a311884ed0e433a464602 usr/bin/foo
cc29c04462ee591b535026935531514f usr/lib/libfoo.so.1.2.3

Lots of multipkg stuff is magic and undocumented.

Questions I've got or have heard:

• what are names of valid scripts?
• what happens if there's no build script?

I'm happy to write this, but @erikwb - can you throw together a list of anything clever you can think of in multipkg?

sudo cpanm install App::Multipkg?

thoughts?

Somewhere along the lines, support for repo bases (-b) on local filesystems got dropped. When using git-multipkg from commit 6ccefbf, the following succeeds:
git-multipkg -b /home/noahm/src multipkg

But with more recent revisions(e.g. b94a318), it fails with
"unsupported base at /usr/bin/git-multipkg line 176."