From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkg_{pre,post}inst misusage
Date: Fri, 23 Dec 2005 19:46:59 +0100 [thread overview]
Message-ID: <20051223184659.GA14896@gentoo.org> (raw)
In-Reply-To: <200512240309.47085.jstubbs@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
On Sat, Dec 24, 2005 at 03:09:47AM +0900, Jason Stubbs wrote:
> On Saturday 24 December 2005 02:52, Harald van Dijk wrote:
> > On Sat, Dec 24, 2005 at 02:22:06AM +0900, Jason Stubbs wrote:
> > > Symlinks are handled within portage differently to regular files. Regular
> > > files get an mtime check and are removed if it matches. Symlinks don't
> > > get an mtime check (even thought the mtime is stored) and are only
> > > removed if the symlink's target doesn't exist. Hence, it seems to be this
> > > way by design. Why it's this way? Who knows. It's been that way for
> > > longer than anyone can remember which is why _it's so important that bugs
> > > get filed_.
> >
> > Honestly, I thought it was supposed to be like that, since
> > collision-protect also doesn't protect against packages overwriting
> > each other's symlinks (package A and package B can both create
> > /dummy -> bin without any problems from portage).
>
> As far as portage source goes, it is meant to be like that. But as far as
> portage source goes, installed package information isn't necessary for dep
> calculation (including depclean)... Most code has been reviewed and the major
> issues are known by at least one person, but there is still some code that
> hasn't suffered a close examination (yet alone reworking) such as the code
> that the above bug hits.
>
> > Do you want a bug report for that?
>
> Yes, please.
Okay, reported as bug #116511.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-23 18:54 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 [this message]
2005-12-23 18:42 ` Thomas de Grenier de Latour
2005-12-23 19:12 ` Jason Stubbs
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=20051223184659.GA14896@gentoo.org \
--to=truedfx@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