Hope Duryea [EMAIL PROTECTED] writes:
--- Ian Jackson [EMAIL PROTECTED] wrote:
Hope Duryea writes (Re: Question about dpkg -r ):
dpkg did not need to create /usr (the symlink),
but it wants to -- and does -- remove it just the
same. As I mentioned before, there are plenty of
other
Ian Jackson [EMAIL PROTECTED] writes:
Goswin von Brederlow writes (Re: Question about dpkg -r):
Ian Jackson [EMAIL PROTECTED] writes:
So this package:
usr
usr/bin
usr/bin/hello
is fine but this one:
usr/bin/hello
is wrong.
Which happens or did happen at some point
--- Goswin von Brederlow
[EMAIL PROTECTED] wrote:
Hope Duryea [EMAIL PROTECTED] writes:
Are you saying debian packages can only be used on
systems where the entire system is comprised
solely of things installed as debian packages?
I was hoping I could use debian packages for
Hope Duryea [EMAIL PROTECTED] writes:
Putting this stuff into /usr/local isn't an option --
but I'm a bit confused about what you mean. How is
/usr/local, if I create it myself, any different from
my creating /usr myself?
There is no package in debian containing /usr/local or anything below
--- Goswin von Brederlow
[EMAIL PROTECTED] wrote:
Hope Duryea [EMAIL PROTECTED] writes:
I don't have a debian system. I have a system
that I had hoped I could install additional files
into, using debian packages to do that.
Then your assumptions and dpkgs assumptions collide.
It
Ian Jackson [EMAIL PROTECTED] writes:
Goswin von Brederlow writes (Re: Question about dpkg -r):
Say foo and bar both use /foobar/. When you install foo dpkg has to
create the directory. When you install bar the directory is already
there. When you purge foo the directory is not empty
Goswin von Brederlow writes (Re: Question about dpkg -r):
Ian Jackson [EMAIL PROTECTED] writes:
So this package:
usr
usr/bin
usr/bin/hello
is fine but this one:
usr/bin/hello
is wrong.
Which happens or did happen at some point. I think it was fixed.
Right, there were
Hope Duryea writes (Re: Question about dpkg -r ):
dpkg did not need to create /usr (the symlink), but it
wants to -- and does -- remove it just the same. As I
mentioned before, there are plenty of other files
under there, but none that came from a debian package.
Oh
--- Ian Jackson [EMAIL PROTECTED] wrote:
Hope Duryea writes (Re: Question about dpkg -r ):
dpkg did not need to create /usr (the symlink),
but it wants to -- and does -- remove it just the
same. As I mentioned before, there are plenty of
other files under there, but none that came from
Hope Duryea writes (Re: Question about dpkg -r ):
There isn't a test up-front to see whether the dir (or
the dir the symlink points to) is empty -- rmdir() is
called just if no other package is using it, and a
test is then done to see if errno was ENOTEMPTY. But
when rmdir() is used
--- Ian Jackson [EMAIL PROTECTED] wrote:
But when rmdir() is used on a symlink, it just
removes the symlink
WTF? Have you verified this with strace ? rmdir(2)
on a symlink should give ENOTDIR.
Sorry, I read the following in a man-page for
rmdir(2):
If path refers to a symbolic link,
* Kris Deugau ([EMAIL PROTECTED]) [070414 00:02]:
Hope Duryea wrote:
The problem is my /usr is actually a symlink,
[snip behaviour explanation]
I have to ask... *Why* do you have /usr as a symlink? Extra partition,
loopback mount, NFS mount I can understand... Symlink I just can't see
The problem is my /usr is actually a symlink, and
despite the fact that it has lots of files and other
subdirs in it (in the real dir it's a link to, that
is), dpkg -r does remove it. So I was trying to think
of some way to prevent that happening.
There's this comment in remove.c:
/* Only delete
Hope Duryea wrote:
The problem is my /usr is actually a symlink,
[snip behaviour explanation]
I have to ask... *Why* do you have /usr as a symlink? Extra partition,
loopback mount, NFS mount I can understand... Symlink I just can't see
being more useful than any of the other three I noted, or
Hope Duryea [EMAIL PROTECTED] writes:
Hi all,
I haven't read through the entire source, but from
what I can tell by using dpkg -r on a package, and
from looking at isdirectoryinuse(), and the call to it
in remove.c, it seems the criteria for whether a
directory is included in the removal
Hope Duryea [EMAIL PROTECTED] writes:
The problem is my /usr is actually a symlink, and
despite the fact that it has lots of files and other
subdirs in it (in the real dir it's a link to, that
is), dpkg -r does remove it. So I was trying to think
of some way to prevent that happening.
%
Hi all,
I haven't read through the entire source, but from
what I can tell by using dpkg -r on a package, and
from looking at isdirectoryinuse(), and the call to it
in remove.c, it seems the criteria for whether a
directory is included in the removal of the package is
whether any other package
Hope Duryea writes...
I haven't read through the entire source, but from
what I can tell by using dpkg -r on a package, and
from looking at isdirectoryinuse(), and the call to it
in remove.c, it seems the criteria for whether a
directory is included in the removal of the package is
whether
18 matches
Mail list logo
