On Thu, 27 Sep 2007 08:08:49 -0600, Bruce Sass <[EMAIL PROTECTED]> said:
> The bit you're still missing is the first part of the question you
> didn't answer: "Is there any situation where ownership has collided"
> IOW: if the file shared by many packages isn't having ownership
> problems there is no need to consider it (no point trying to fix
> something that is not broken, eh).
The start of this thread was a rant about not loose files
floating around in /etc; not necessarily about whether these files in
themselves had ownership problems (whtever that means).
Here is the original context. Note how you say the problem
(actually, design flaw) is about current tools do not "catch files
created by Maintainer scripts"?
Nice to see the design flaw has become stuff that is not broken
and does not have to be fixed. That is all I cared about, really.
manoj
On Fri, 21 Sep 2007 03:25:23 +0000 (UTC), Oleg Verych (Gmane)
<[EMAIL PROTECTED]> said:
> 19-09-2007, Bruce Sass: []
>>> > I like this too. Finding what a package has just installed is one
>>> > of the biggest holes in Debian right now, IMO. I have to use dpkg
>>> > -L to figure this out, and that's just too crude to be a real
>>> > solution.
>>>
>>> Too crude? That's a simple command, easily found in a relevant
>>> manpage. In true Unix fashion, its output can be easily piped to
>>> other commands. What's crude about it?
>>
>> It doesn't catch files created by Maintainer scripts?
> This is the design flaw in those scripts (even in whole package
> management).
--
You know how to win a victory, Hannibal, but not how to use it. Maharbal
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
