public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yannick Le Saint (kyncani)" <y.lesaint@free.fr>
To: gentoo-portage-dev@gentoo.org
Subject: [gentoo-portage-dev] Specific build permanent environment
Date: Mon, 08 Dec 2003 09:59:11 +0000	[thread overview]
Message-ID: <1070877548.4784.21.camel@kyncani.lesaint> (raw)


 Hi, first of all, i'd like to say how much i appreciate the goals of
portage-ng's rewrite :)

 That having said, i would like to be able to specify a specific build
environment for some packages, manually modifying the environment for
emerge is just not sufficient.

 May i propose a /etc/portage/portage.d directory, where i could create,
say a /etc/portage/portage.d/net-fs/samba/make.conf file which would
modify the normal build environment.

 for example, my /etc/portage/portage.d/net-fs/samba/make.conf file
would contain :

 USE="-ldap"

 this way i know that if samba gets upgraded, i won't have to recompile
it myself with USE="-samba" emerge ... samba.

 and maybe even a /etc/portage/portage.d/net-misc/jigdo/make.conf file
with :

 ACCEPT_KEYWORDS="~x86"

 so that if jigdo gets updated in ~x86 and i run x86 keywords (i do),
jigdo will get updated (portage would know that i build jigdo with
~x86).


 Yeah, that's it, with maybe some mechanism to provide slot-specific
informations, maybe ...



--
gentoo-portage-dev@gentoo.org mailing list


             reply	other threads:[~2003-12-08  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08  9:59 Yannick Le Saint (kyncani) [this message]
2003-12-08 15:27 ` [gentoo-portage-dev] Specific build permanent environment Andrew Gaffney
2003-12-08 15:27 ` Yannick Le Saint (kyncani)

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=1070877548.4784.21.camel@kyncani.lesaint \
    --to=y.lesaint@free.fr \
    --cc=gentoo-portage-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