Does anyone knows about emerge --inject equivalent? Inject was used to
tell (lie to) portage that some package is installed alhough it is
not.
What I was to trying to do is to avoid recompilation of the whole
glibc because new flag fas been added to CROSSCOMPILE_OPTIONS.
emerge -uDN world keeps
On Tue, 8 Jul 2008 18:14:13 +0200
Marko Kocić [EMAIL PROTECTED] wrote:
Does anyone knows about emerge --inject equivalent? Inject was used to
tell (lie to) portage that some package is installed alhough it is
not.
What I was to trying to do is to avoid recompilation of the whole
glibc
Does that mean that I will be prompted to recompile when some flag
that is used is changed or when new version becomes available?
Thanks,
Marko
2008/7/8 Kenneth Prugh [EMAIL PROTECTED]:
On Tue, 8 Jul 2008 18:14:13 +0200
Marko Kocić [EMAIL PROTECTED] wrote:
Does anyone knows about emerge
On Tue, 8 Jul 2008 18:14:13 +0200, Marko Kocić wrote:
The same story applies to different packages. If new USE flag is added
which I don't use anyways, I still have to recompile the same version
of package because emerge bugs me to do it.
Does anyone knows how to avoid unnecessary
Thanks,
the problem is that USE flags are not changed, but CROSSCOMPILE_HEADER_OPTIONS
New option is added there which is not used anyways.
I'll try that as soon as I can.
The same story applies to different packages. If new USE flag is added
which I don't use anyways, I still have to
On Tue, 8 Jul 2008 18:34:53 +0200
Marko Kocić [EMAIL PROTECTED] wrote:
Does that mean that I will be prompted to recompile when some flag
that is used is changed or when new version becomes available?
from the man page:
Portage will not attempt to update a package that is listed here unless
On Tue, 8 Jul 2008 18:42:57 +0200, Marko Kocić wrote:
the problem is that USE flags are not changed, but
CROSSCOMPILE_HEADER_OPTIONS New option is added there which is not used
anyways.
The other options can also be changed in files in the same directory.
Please don't top post, unless
7 matches
Mail list logo