public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: pkg_{pre,post}inst misusage
Date: Fri, 23 Dec 2005 11:43:01 -0700	[thread overview]
Message-ID: <pan.2005.12.23.18.43.00.666301@cox.net> (raw)
In-Reply-To: 200512240222.06574.jstubbs@gentoo.org

Jason Stubbs posted <200512240222.06574.jstubbs@gentoo.org>, excerpted
below,  on Sat, 24 Dec 2005 02:22:06 +0900:

> A quick patch makes symlinks handled similarly to regular files and
> solves the issue. I'll put it into testing unless anybody can come up
> with a reason not to. The case that will be broken by the patch is when
> two different packages install the same symlink. PackageA is
> installed, PackageB is installed, PackageB is uninstalled -> PackageA is
> broken. Does this case exist?

Yikes!  That's not going to remove /lib or /usr/lib or the like, for us on
amd64, where that's a symlink to lib64, will it?

equery b /lib
[ Searching for file(s) /lib in *... ]
net-analyzer/macchanger-1.5.0-r1 (/lib)
sys-apps/baselayout-1.12.0_pre12 (/lib)
sys-boot/grub-0.97 (/lib)
sys-devel/gcc-4.0.2-r1 (/lib)
sys-devel/gcc-3.4.4-r1 (/lib)
sys-fs/device-mapper-1.01.05 (/lib)
sys-fs/lvm2-2.01.14 (/lib)
sys-fs/udev-078 (/lib)
sys-libs/glibc-2.3.6 (/lib)

There's a similar, longer list, for  /usr/lib.  Obviously, not all of
those will own it as a symlink, but it is one, and if removing one happens
to remove the symlink...

Also consider the effect where a former dir is now a symlink or a former
symlink is now a dir.  The recent xorg directory moves come to mind.

You are /sure/ the new code won't screw anything of that sort up, right?
Maybe that's the reason nobody seems to have been around to know about.
It just sounds like it /could/ be dangerous to me.  For some reason, I
don't like the idea of something that could hose a system that badly!  =8^\

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-12-23 18:55 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
2005-12-23 18:43             ` Duncan [this message]
2005-12-23 18:57               ` [gentoo-dev] " 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=pan.2005.12.23.18.43.00.666301@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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