--On Wednesday, April 27, 2005 11:51 AM -0400 Chip Turner
<cturner@xxxxxxxxxxx> wrote:
Your wish is my command. cpanflute2 will now inspect the tarball
(assuming it can; gotta have perl-Archive-Tar and perl-IO-Zlib). If
the first directory of every file in the tarball is consistent, then
that is what will be passed to %setup (with the version replaced with
%{version}, if possible). It falls back to the old behavior if it
cannot determine a common prefix. Will this suffice for your needs?
Thanks, that's great!
<http://search.cpan.org/~domizio/CGI-Builder-1.26+/lib/Bundle/CGI/Builde
r/Complete.pm>
Was what was blocking you the manpage thing and the %setup directory,
or something else?
More the sheer number of packages and the entwined dependency tree to build
it all. With RPM I have to download and package something, discover the
dependency, download, package and install the dependency, then discover its
dependencies.... All intertwined with su'ing between my packaging mortal
and root. Very tedious.
At least with Perl modules I don't need to worry about inspecting
%pre/%post scripts, but I do worry that a rogue Makefile could do something
bad as root. I'd rather do all the packaging as a mortal and then install
everything from RPM packages as root. (Makefiles can silently overwrite
things, while RPM will block the install on conflicts, and will record
everything that it installs.) I suppose it would be acceptable if an
automated mechanism sudo'd to install the dependencies as they were
packaged. (Of course CPAN.pm has the problem that it must run as root to
make and install all the dependencies along the way, so packaging RPM's as
root would be no worse than what we have now.)
