public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Config dir protection
Date: Mon Jul 30 11:57:01 2001	[thread overview]
Message-ID: <8766cab8ui.fsf@codefactory.se> (raw)
In-Reply-To: <20010730114117.M14345@cvs.gentoo.org>

Daniel Robbins <drobbins@gentoo.org> writes:

> On Mon, Jul 30, 2001 at 07:20:07PM +0200, Mikael Hallendal wrote:
> > Dan Armak <danarmak@gentoo.org> writes:
> > 
> > Gnome stuff put there in /opt/gnome/etc which is a symlink to
> >/etc/opt/gnome, wouldn't it be good to have /etc/opt/kde and have
> >/opt/kde/share/config point there?
> > 
> > What I wonder is what will portage do when it installs into
> >/opt/gnome/etc and that is a symlink (to a protected directory). Will
> >it see that the files should be protected or does it think that it's
> >an unprotected directory? We wan't it to behave in the first way.
> 
> Hallski; I'm sure portage has the bug you just described.  Could you
> add it to the wiki and assign it to the System team?  Fixing it will
> be tricky.  The best fix may be to have some standards about how/where
> to create config directories and what is/isn't allowed to be a
> symlink.

That might be the best way of doing it yes. We must however fix
portage to handle this in some way. 

Regards,
Mikael Hallendal

-- 
Mikael Hallendal                micke@codefactory.se
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918




      reply	other threads:[~2001-07-30 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 10:41 [gentoo-dev] Config dir protection Dan Armak
2001-07-30 10:54 ` Daniel Robbins
2001-07-30 11:50 ` Mikael Hallendal
2001-07-30 11:42   ` Daniel Robbins
2001-07-30 11:57     ` Mikael Hallendal [this message]

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=8766cab8ui.fsf@codefactory.se \
    --to=hallski@gentoo.org \
    --cc=gentoo-dev@cvs.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