Willie Wong wrote:
On Thu, Nov 24, 2005 at 11:01:43AM -0800, glen martin wrote:
Seems a truism, but you're right. apache isn't in my world file.
somehow. And adding it to my world file does work around the symptom I
describe.
This begs the question of why it isn't there, considering it is
glen martin schreef:
As an aside, I wonder whether it is a good feature idea that
ACCEPT_KEYWORDS=keyword emerge foo without --oneshot should
automatically add foo keyword to the package.keywords file.
That's an idea with some merit, but imo not enough (merit) to make it
feasible (but
Holly Bostick wrote:
glen martin schreef:
As an aside, I wonder whether it is a good feature idea that
ACCEPT_KEYWORDS=keyword emerge foo without --oneshot should
automatically add foo keyword to the package.keywords file.
That's an idea with some merit, but imo not enough (merit) to
glen martin schreef:
Holly Bostick wrote:
glen martin schreef:
As an aside, I wonder whether it is a good feature idea that
ACCEPT_KEYWORDS=keyword emerge foo without --oneshot should
automatically add foo keyword to the package.keywords file.
That's an idea with some merit, but imo
On Fri, 25 Nov 2005 06:16:40 -0800, glen martin wrote:
As an aside, I wonder whether it is a good feature idea that
ACCEPT_KEYWORDS=keyword emerge foo
without --oneshot should automatically add foo keyword to the
package.keywords file.
It's a bad idea. Specifying a setting on the command
On 11/25/05, Holly Bostick [EMAIL PROTECTED] wrote:
The idea of having the temporary setting invisibly add a permanent
setting seems cool, but undermines both the function of the temporary
setting (since it's no longer truly temporary), and the function of the
permanent setting (since you have
I've googled and scanned recent messages archive of this list for this
issue - if I'm blind, apologies in advance.
I've changed some USE flags deliberately to add features to a package
(in this case, apache). That package is also impacted by different
ACCEPT_KEYWORDS flag (~86), which I've
glen martin schreef:
snip
I've changed some USE flags deliberately to add features to a package
snip
Despite the USE change, I find that that apache is not being caught
by emerge --newuse world.
snip
I added threads nptlonly mpm-worker to USE in make.conf. I've
probably made some
On Thursday 24 November 2005 15:52, glen martin wrote:
I've googled and scanned recent messages archive of this list for this
issue - if I'm blind, apologies in advance.
I've changed some USE flags deliberately to add features to a package
(in this case, apache). That package is also
glen martin wrote:
note the lack of apache. Now:
snip
# emerge --pretend --verbose apache
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] net-www/apache-2.0.55 +apache2 -debug -doc +ldap
-mpm-leader -mpm-peruser -mpm-prefork
Holly Bostick wrote:
So, any thoughts on why emerge --newuse doesn't want to rebuild
apache?
Well, assuming it's not a bug (what version of Portage are you using?)
then is it possible that apache is neither in your world file,
I'm on portage 2.0.51.22-r3. This is a very new system -
On Thu, Nov 24, 2005 at 11:01:43AM -0800, glen martin wrote:
Seems a truism, but you're right. apache isn't in my world file.
somehow. And adding it to my world file does work around the symptom I
describe.
This begs the question of why it isn't there, considering it is
installed. I must
On Thu, 24 Nov 2005 11:01:43 -0800, glen martin wrote:
This begs the question of why it isn't there, considering it is
installed. I must wonder, what else that I've installed has somehow not
been added to the world file. Perhaps I'm exposing my ignorance, but is
the world file not supposed
13 matches
Mail list logo
