public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Vanilla behaviour in Gentoo Linux (long email)
Date: Wed, 5 Nov 2003 11:48:33 +0100	[thread overview]
Message-ID: <20031105114833.463cbcb0.degrenier@easyconnect.fr> (raw)
In-Reply-To: <20031104114926.GA8710@netswarm.net>

On Tue, 4 Nov 2003 12:49:26 +0100
Christian Birchinger <joker@gentoo.org> wrote:

> Yes, the same feature would be used to block installs into
> /usr/share/doc or /usr/share/info. I think we called it
> INSTALL_PROTECT in the previous discution about "noman" etc.
> I know a totaly different topic but could be done with the same
> portage feature.

If you want you can try this patch:
http://bugs.gentoo.org/show_bug.cgi?id=32780

But sorry, I've called it "MERGE_EXCLUDE", because I've made the
first version of this patch before the consensus on the name, and was
too lazy to change it :)

-- 
TGL.

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-11-05 10:48 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03  1:29 [gentoo-dev] Vanilla behaviour in Gentoo Linux (long email) Dhruba Bandopadhyay
2003-11-03  2:01 ` Brad House
2003-11-04 23:06   ` Steven Elling
2003-11-04 23:54     ` William Kenworthy
2003-11-07 23:24       ` Steven Elling
2003-11-08  0:09         ` Spider
2003-11-05  1:00     ` Terje Kvernes
2003-11-05  9:24       ` Paul de Vrieze
2003-11-05 11:46         ` Terje Kvernes
2003-11-06 15:47       ` Anthony de Boer
2003-11-06 17:01         ` Marius Mauch
2003-11-07 23:29       ` Steven Elling
2003-11-07 23:55         ` Eldad Zack
2003-11-03  2:16 ` Jon Portnoy
2003-11-03  8:49   ` Toby Dickenson
2003-11-03 16:36   ` Markus Nigbur
2003-11-03 17:02     ` Philippe Coulonges
2003-11-03 17:17       ` Caleb Tennis
2003-11-05  0:43   ` Anthony de Boer
2003-11-05  1:11     ` Camille Huot
2003-11-03  2:19 ` Chris Smith
2003-11-03  3:33   ` C. Brewer
2003-11-03  3:45     ` Jon Portnoy
2003-11-03  6:31       ` C. Brewer
2003-11-03  6:40         ` Jon Portnoy
2003-11-03  7:03           ` C. Brewer
2003-11-03  5:55 ` [gentoo-dev] " Björn Lindström
2003-11-03  6:33   ` Spider
2003-11-03 11:15     ` purslow
2003-11-03  8:44 ` [gentoo-dev] " Donnie Berkholz
2003-11-03  9:37   ` Paul de Vrieze
2003-11-03 10:11     ` Antonio Dolcetta
2003-11-03  9:39 ` Robin H. Johnson
2003-11-03 15:36 ` Matthew Kennedy
2003-11-03 15:58 ` Matthew Kennedy
2003-11-03 17:55   ` Mike Frysinger
2003-11-03 21:01     ` Martin Schlemmer
2003-11-03 18:40   ` Donnie Berkholz
2003-11-03 18:47     ` Mike Frysinger
2003-11-04  5:49       ` Donnie Berkholz
2003-11-04 19:04         ` Marius Mauch
2003-11-03 16:25 ` Luca Barbato
2003-11-04  6:31 ` Jesper Fruergaard Andersen
2003-11-04  7:08   ` Troy Dack
2003-11-04 10:03     ` Paul de Vrieze
2003-11-04 11:49       ` Christian Birchinger
2003-11-05 10:48         ` Thomas de Grenier de Latour [this message]
2003-11-05 12:03           ` Christian Birchinger
2003-11-04 17:18       ` Martin Schlemmer
2003-11-04 10:08     ` Thomas de Grenier de Latour
2003-11-04 17:15   ` Martin Schlemmer
2003-11-04  7:34 ` Troy Dack
2003-11-04  8:04   ` C. Brewer
2003-11-04 10:08     ` Paul de Vrieze

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=20031105114833.463cbcb0.degrenier@easyconnect.fr \
    --to=degrenier@easyconnect.fr \
    --cc=gentoo-dev@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