On 1/11/06, Aron Griffis <[EMAIL PROTECTED]> wrote:
> Bug 9849 has been marked a duplicate of 23851, but there is
> a distinction between the two: 23851 would be "solved" by pre-failing
> the merge phase if it is predicted to fail (permissions, diskspace).
> But 9849 is pretty specific to .keep fil
Donnie Berkholz wrote: [Sat Jan 07 2006, 06:20:48PM EST]
> That's actually not the case; I've never gotten around to filing a bug
> for it, but I mount my /media read-only (so I don't accidentally delete
> all my music) and pmount dies every time.
AFAIK, the original bug pertaining to this issue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefaan wrote:
| I don't use pmount myself, but my guess is that /media is just a
| directory that contains mountpoints, and which remains at all time
| writeable for root. /afs is not writeable when mounted, just like
| /dev/cdrom etc...
That's actu
On 1/7/06, Petteri Räty <[EMAIL PROTECTED]> wrote:
> Stefaan wrote:
> > The obvious solution seems to do "keepdir", so portage would attempt
> > to make the directory and put a .keep file in there. I say attempt,
> > because the following problem will occur during an re-merge or
> > upgrade, while
Petteri Räty wrote:
> Stefaan wrote:
>
>>Hi!
>>
>>I'm having an issue with the openafs-ebuild, and I don't see a
>>solution for the moment. I wondered if someone on the list would:
>>
>>Prerequisite:
>>The ebuild needs to create the /afs directory, and remove that same
>>directory when it is unins
Stefaan wrote:
> Hi!
>
> I'm having an issue with the openafs-ebuild, and I don't see a
> solution for the moment. I wondered if someone on the list would:
>
> Prerequisite:
> The ebuild needs to create the /afs directory, and remove that same
> directory when it is uninstalled.
>
> The obvious
Stefaan wrote:
You suggest keeping the /afs dir, this would be an easy solution of
course, but it does seem untidy, doesn't it? (Makes me think of the
windows uninstallers saying "not all files could be removed, have a
nice day")
Ah, I of course didn't pay enough attention and didn't reali
On 1/7/06, Brian Jackson <[EMAIL PROTECTED]> wrote:
> You could handle it the way the baselayout ebuild does.
But baselayout also just creates the directories in pkg_postinst (if
my interpretation of the ebuild is correct). The list is not kept, so
when uninstalling baselayout the directories are
On 1/7/06, Joshua Baergen <[EMAIL PROTECTED]> wrote:
> Why not just create the directory in ${D} or ${IMAGE} and let Portage
> handle the rest? Do you really want to be removing /afs unconditionally
> on unmerge?
Because this results in this: (directory /t existed and /dev/cdrom was
mounted to it
You could handle it the way the baselayout ebuild does.
--Iggy
Stefaan wrote:
Hi!
I'm having an issue with the openafs-ebuild, and I don't see a
solution for the moment. I wondered if someone on the list would:
Prerequisite:
The ebuild needs to create the /afs directory, and remove that same
Stefaan wrote:
Prerequisite:
The ebuild needs to create the /afs directory, and remove that same
directory when it is uninstalled.
Why not just create the directory in ${D} or ${IMAGE} and let Portage
handle the rest? Do you really want to be removing /afs unconditionally
on unmerge?
Josh
Hi!
I'm having an issue with the openafs-ebuild, and I don't see a
solution for the moment. I wondered if someone on the list would:
Prerequisite:
The ebuild needs to create the /afs directory, and remove that same
directory when it is uninstalled.
The obvious solution seems to do "keepdir", so
12 matches
Mail list logo
