On Dec 7, 2004, at 1:54 PM, Stephen Quinney wrote:
On Tue, Dec 07, 2004 at 07:17:34AM -0500, Michael G Schwern wrote:Is it save to 'replace' a file, even if the client installing it doesn't have it yet?On Tue, Dec 07, 2004 at 10:18:12AM +0100, Jos I. Boumans wrote:
While building these .debs we've got very encouraging results, and barring debian policy option tweaks, they're 'technically' sound. However, one issue arises: The debian package system does not allow a file to be 'owned' (or provided) by 2 different packages, which is a problem when updating core modules from CPAN (like for example Test::More and Cwd):
They can. I believe you want to look at "Replaces".
http://www.debian.org/doc/debian-policy/ch-relationships.html#s- replaces
Except if their target install dir is "PERL", which i think the rules override, but i'm not sureThere's also "diversions" as well as "alternatives". http://www.debian.org/doc/debian-policy/ap-pkg-diversions.html
It should also be noted that "core" Perl modules go into a different directory to the individual packages.
Individual packages:
/usr/lib/perl5 /usr/share/perl5
"core" modules:
/usr/lib/perl/5.8 /usr/share/perl/5.8
So there is nothing preventing someone updating a core module with a new, more recent, version in a separate package.
-- they set DESTDIR=vendor (schwern?)
If you look at the failure, you'll see it was actually a script though that failed to
install, and i'm afraid they all go into the same bin dir...
dpkg: error processing libtest-harness-perl_2.42-1_all.dâeb (--install):
trying to overwrite `/usr/bin/prove', which is also in package perl
Errors were encountered while processing:
libtest-harness-perl_2.42-1_all.deb
So here there *is* a conflict...
--
Jos Boumans'Real programmers use "cat > a.out"'
CPANPLUS http://cpanlus.sf.net

