From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkg_{pre,post}inst misusage
Date: Sat, 24 Dec 2005 04:12:52 +0900 [thread overview]
Message-ID: <200512240412.52131.jstubbs@gentoo.org> (raw)
In-Reply-To: <20051223194238.3cbd8e64@eusebe>
On Saturday 24 December 2005 03:42, Thomas de Grenier de Latour wrote:
> On Sat, 24 Dec 2005 02:22:06 +0900
>
> Jason Stubbs <jstubbs@gentoo.org> wrote:
> > PackageA is installed, PackageB is installed, PackageB is
> > uninstalled -> PackageA is broken. Does this case exist?
>
> Found two on my system:
>
> * "/usr/lib/X11/app-defaults -> /etc/X11/app-defaults" is
> installed by several X11 apps (media-gfx/xfig, x11-misc/seyon,
> x11-misc/xvkbd, and i would not be surprised there are others)
This looks like something that a lower level X ebuild should be installing.
The problem here is that there's also a bit of funny business going on when
portage encounters a merge of some filetype being blocked by a different
filetype. In the above case, if some X11 package installs
the /usr/lib/X11/app-defaults symlink and all other apps install
to /etc/X11/app-defaults then everything should be fine.
> * "/usr/share/cups/model/foomatic-ppds -> /usr/share/ppd" is
> installed by both net-print/foomatic-db and net-print/hplip.
Again, given the name of the symlink, net-print/hplip should probably be
installing directly to /usr/share/ppd.
> Maybe this particular packages could be hacked to avoid need for
> the symlinks (or the symlinks should be installed only by some
> lower level, depended-on, packages?), but anyway it would be hard
> to do a strict sanity check of the whole tree. And letting that to
> "collision-protect" feature doesn't sound really like a short term
> solution neither. So, basically, i don't see how you could safely
> change this portage behavior atm (although i agree it would be a
> good thing once done).
Yep, it seems that changing the behaviour will lead to some breakage. However
repoman is definately not capable of handling this sort of stuff. Also, none
of the breakage (that you've revealed here at least) is that bad. Putting the
relevant collision-protect changes into ~arch and following up with the
actual unmerge changes should lead to minimal disruption on the user's side.
--
Jason Stubbs
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-23 19:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 10:10 [gentoo-dev] pkg_{pre,post}inst misusage Jason Stubbs
2005-12-23 11:19 ` Stefan Schweizer
2005-12-23 11:31 ` Jason Stubbs
2005-12-23 12:39 ` Harald van Dijk
2005-12-23 12:55 ` Jason Stubbs
2005-12-23 13:00 ` Jason Stubbs
2005-12-23 13:13 ` Harald van Dijk
2005-12-23 17:11 ` Zac Medico
2005-12-23 17:32 ` Jason Stubbs
2005-12-23 17:22 ` Jason Stubbs
2005-12-23 17:52 ` Harald van Dijk
2005-12-23 18:09 ` Jason Stubbs
2005-12-23 18:46 ` Harald van Dijk
2005-12-23 18:42 ` Thomas de Grenier de Latour
2005-12-23 19:12 ` Jason Stubbs [this message]
2005-12-23 18:43 ` [gentoo-dev] " Duncan
2005-12-23 18:57 ` Simon Stelling
2005-12-23 19:06 ` Jason Stubbs
2005-12-23 21:19 ` [gentoo-dev] " Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512240412.52131.jstubbs@gentoo.org \
--to=jstubbs@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox