On Tue, 19 May 2009, Danek Duvall wrote:
On Tue, May 19, 2009 at 09:50:36AM +0200, Robert Milkowski wrote:
See http://defect.opensolaris.org/bz/show_bug.cgi?id=9014 for more details
on the failure.
So like you saw, that's a duplicate of 3644.
I could mv %build/usr/lib/X11 to %build/usr/X11 in the install section of
spec files and update %files accordingly but it doesn't seem right. pkg
should be able to handle it properly.
The fix I was planning on was to prevent the second package from installing
-- that is, the first package to install a path on the system can make it
either a symlink or a directory, but after that, all other packages need to
treat it the same way (actually, in the case of a symlink, it shouldn't be
allowed to duplicate, given bug 2369).
Or is there some other behavior you'd rather see?
I guess it is the only sensible approach.
However what would be nice to have is a tool on jucr and other
repositories which would fetch all manifests and check for such conflicts
(maybe as para of a build process?) and would not allow to publish a
package with such a conflict in a fist place.
Otherwise we will end up with situation where user will be able to install
package A or B but not both... it shouldn't happen with the packages
coming from official repositories.
--
Robert Milkowski
http://milek.blogspot.com
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
