public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] We have "doc" USE flag, why not a "man" USE flag too
Date: Thu, 11 Aug 2005 15:40:53 +0200	[thread overview]
Message-ID: <20050811154053.3cc07279@sven.genone.homeip.net> (raw)
In-Reply-To: <200508110826.49908.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

On Thu, 11 Aug 2005 08:26:49 -0400
Mike Frysinger <vapier@gentoo.org> wrote:

> On Thursday 11 August 2005 07:02 am, Jason Stubbs wrote:
> > With noman and the like, how's the following for a solution? A lot
> > of the ebuild functions contained within portage will be moving
> > into the tree once signing is in. What about adding
> > {pre,post}_src_{compile,install,...} hooks into portage that will
> > live in the tree that USE="man" support can be implemented in
> > globally? For those packages that have a specific interest, the USE
> > flag will be available. Everything should be happy on the ebuild
> > side of things. (On the U/I side of things, stuff can be done to
> > cut down the noise.)
> 
> so you're saying that the default ebuild.sh functions are going to be
> moving into the tree to a place which will be auto-sourced before the
> ebuild and its eclasses ?
> -mike

If you read it again you'll notice the {pre,post} part ;)
IIRC that's already in HEAD for /etc/portage/bashrc, so extending it to
$PORTDIR shouldn't be an issue.

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-11 13:41 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 12:09 [gentoo-dev] We have "doc" USE flag, why not a "man" USE flag too Bjarke Istrup Pedersen
2005-08-10 12:16 ` Jakub Moc
2005-08-10 12:19 ` Diego 'Flameeyes' Pettenò
2005-08-10 12:20 ` Daniel Drake
2005-08-10 13:10   ` Michael Cummings
2005-08-10 13:16     ` Mike Frysinger
2005-08-10 15:14       ` Diego 'Flameeyes' Pettenò
2005-08-10 15:57         ` Georgi Georgiev
2005-08-10 13:19     ` Ciaran McCreesh
2005-08-10 14:58       ` Mike Frysinger
2005-08-10 15:24       ` Jason Stubbs
2005-08-10 15:31         ` Ciaran McCreesh
2005-08-10 16:06           ` Carsten Lohrke
2005-08-10 16:16             ` Ciaran McCreesh
2005-08-10 16:19             ` Diego 'Flameeyes' Pettenò
2005-08-10 17:07               ` Carsten Lohrke
2005-08-10 17:26                 ` Mike Frysinger
2005-08-10 17:38                   ` Henrik Brix Andersen
2005-08-10 18:13                   ` Carsten Lohrke
2005-08-10 18:22                     ` Mike Frysinger
2005-08-10 17:45                 ` Ciaran McCreesh
2005-08-10 18:25                   ` Carsten Lohrke
2005-08-10 18:33                     ` Mike Frysinger
2005-08-10 18:35                     ` Ciaran McCreesh
2005-08-10 18:54                       ` Carsten Lohrke
2005-08-10 19:04                         ` Ciaran McCreesh
2005-08-10 19:29                           ` Carsten Lohrke
2005-08-10 20:01                             ` Mike Frysinger
2005-08-10 23:59           ` Jason Stubbs
2005-08-10 15:34         ` Simon Stelling
2005-08-10 15:39         ` Mike Frysinger
2005-08-10 23:56           ` Jason Stubbs
2005-08-11  0:04             ` Mike Frysinger
2005-08-11 11:02               ` Jason Stubbs
2005-08-11 12:26                 ` Mike Frysinger
2005-08-11 13:40                   ` Marius Mauch [this message]
2005-08-11 14:03                     ` Mike Frysinger
2005-08-11 15:33                       ` Marius Mauch
2005-08-12  1:16                   ` Jason Stubbs
2005-08-10 13:22     ` Diego 'Flameeyes' Pettenò

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=20050811154053.3cc07279@sven.genone.homeip.net \
    --to=genone@gentoo.org \
    --cc=gentoo-dev@lists.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