Summary: | emerge manpage --with-bdeps needs equals | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Duncan <1i5t5.duncan> |
Component: | Documentation | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Duncan
2006-10-02 00:29:32 UTC
(In reply to comment #0) > current manpage: > --with-bdeps < y | n > Actually, it works either way. We're using python's optparse module and it accepts either --with-bdeps=y or --with-bdeps y style syntax. Quite nice, isn't it? > Set up FEATURES=without-bdeps and/or FEATURES=with-bdeps I'm reluctant to add an emerge specific option to FEATURES. It doesn't affect any part of portage beyond emerge, so I don't see a compelling reason to stick it in FEATURES (FEATURES is really quite bloated as it is). I'd prefer to reserve FEATURES for options that truely need to be "global". (In reply to comment #1) > (In reply to comment #0) > > current manpage: > > --with-bdeps < y | n > > > Actually, it works either way. We're using python's optparse module and it > accepts either --with-bdeps=y or --with-bdeps y style syntax. Quite nice, > isn't it? Oops. Typo on my part. I had EMERGE_DEFAULT_OPTS-"--with-bdeps y" and got the following error, only I misinterpreted the "=" reference, and with -"--with-bdeps=y" I no longer got the error, tho it was still incorrect as it had a dash in place of the equals after EMERGE_DEFAULT_OPTS. Since putting =y eliminated the error, I thought sure that was the problem. =8^( !!! Invalid token (not "=") y" !!! "ParseError: Invalid token (not '='): /etc/make.conf: line 21 in /etc/make.conf" !!! Incorrect multiline literals can cause this. Do not use them. I still think it belongs in features, but see your point on that, and since the above was PEBKAC, closing as such. Sorry, but thanks for the help and quick turnaround. Duncan |