On Tue, 2013-12-03 at 18:38 +0100, René Neumann wrote:
> Am 03.12.2013 17:05, schrieb Mike Frysinger:
> > as for the patch, i'm of the opinion that make.conf is not for
> > documenting random USE_EXPAND-ed variables.
> >
> > this sort of thing should go into the relevant eclass,
> > python-r1.ecla
On Tuesday 03 December 2013 11:52:47 Robin H. Johnson wrote:
> On Tue, Dec 03, 2013 at 11:05:51AM -0500, Mike Frysinger wrote:
> > as for the patch, i'm of the opinion that make.conf is not for
> > documenting random USE_EXPAND-ed variables.
>
> ...
>
> > there is the matter of visibility ... we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.12.2013 17:05, schrieb Mike Frysinger:
> as for the patch, i'm of the opinion that make.conf is not for
> documenting random USE_EXPAND-ed variables.
>
> this sort of thing should go into the relevant eclass,
> python-r1.eclass in this case. th
On Tue, Dec 03, 2013 at 11:05:51AM -0500, Mike Frysinger wrote:
> as for the patch, i'm of the opinion that make.conf is not for documenting
> random USE_EXPAND-ed variables.
...
> there is the matter of visibility ... we could add a generic pointer to the
> make.conf man page discussing that the
On Tuesday 03 December 2013 04:19:27 Alexander Berntsen wrote:
> Using git send-email since vapier told me to. I haven't used this before,
> so sorry if I have done something wrong. Please let me know.
looks ok from `git send-email` pov, but random comments not meant for the
commit message should
On Tue, 2013-12-03 at 11:43 +0100, Alexander Berntsen wrote:
> On 03/12/13 11:21, Sebastian Luther wrote:
> > The problem with all these variables is that we don't maintain
> > them. If they disappear, change meaning or new ones are added we
> > constantly have to fix our documentation.
> I don't t
Portage's documentation is inappropriate place for this.
Please do not commit this patch.
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
Alexander Berntsen posted on Tue, 03 Dec 2013 11:43:42 +0100 as excerpted:
> On 03/12/13 11:21, Sebastian Luther wrote:
>> The problem with all these variables is that we don't maintain them. If
>> they disappear, change meaning or new ones are added we constantly have
>> to fix our documentation.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/12/13 11:21, Sebastian Luther wrote:
> The problem with all these variables is that we don't maintain
> them. If they disappear, change meaning or new ones are added we
> constantly have to fix our documentation.
I don't think this is a problem
Am 03.12.2013 11:08, schrieb Alexander Berntsen:
> On 03/12/13 10:46, Sebastian Luther wrote:
>> Should we really document specific USE_EXPAND variables? What
>> about all the others?
> I think so, yes.
>
[...]
> I can do this over the weekend.
>
The problem with all these variables is that we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/12/13 10:46, Sebastian Luther wrote:
> Should we really document specific USE_EXPAND variables? What
> about all the others?
I think so, yes.
> USE_EXPAND="ABI_MIPS ABI_X86 ALSA_CARDS APACHE2_MODULES
> APACHE2_MPMS CALLIGRA_FEATURES CAMERAS CO
Should we really document specific USE_EXPAND variables? What about all
the others?
USE_EXPAND="ABI_MIPS ABI_X86 ALSA_CARDS APACHE2_MODULES APACHE2_MPMS
CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CROSSCOMPILE_OPTS CURL_SSL
DRACUT_MODULES DVB_CARDS ELIBC ENLIGHTENMENT_MODULES FCDSL_CARDS FFTOOLS
FO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Apparently I forgot to turn off the option that CCs the author, and
consequently managed to do what I have been telling you to not do.
Don't take this as an invitation to CC me after all. ;-)
- --
Alexander
alexan...@plaimi.net
http://plaimi.net/~a
Using git send-email since vapier told me to. I haven't used this before, so
sorry if I have done something wrong. Please let me know.
---
man/make.conf.5 | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/man/make.conf.5 b/man/make.conf.5
index c271d17..db198f9 10
14 matches
Mail list logo
