Neil Bothwick wrote:
On Tue, 05 Jul 2011 23:22:05 -0500, Dale wrote:
Wouldn't this be like putting package.* back to a file instead of a
directory tho? That would seem like one step forward and two steps
back. Maybe I am missing something again. I sort of got some issues
going on around
On Wed, 06 Jul 2011 02:52:05 -0500, Dale wrote:
No, the discussion is about the name of the file in package.unmask. if
that is a file there is no issue. The problem is that portage just
picks a file from that directory, it should either have its own file
in there or add the entries to a
On Tue, 05 Jul 2011 23:22:05 -0500, Dale wrote:
Wouldn't this be like putting package.* back to a file instead of a
directory tho? That would seem like one step forward and two steps
back. Maybe I am missing something again. I sort of got some issues
going on around here. :/
No, the
On 05.07.2011 17:58, Dale wrote:
I was using autounmask to do this and it does just like you want.
However, the last time I used autounmask, it was different. You may
want to try that tho to see if it helps in some way.
The feature with emerge picks the first file I think in the
directory.
Hi
I was really looking forward to the new autounmask feature in portage,
as it replaces my ugly home-grown bash script. However, it just picks a
seemingly random file in /etc/portage/package.keywords to put things
into. Is there a way to specify which file it writes things into?
Ideally, I
Gian Calgeer wrote:
Hi
I was really looking forward to the new autounmask feature in portage,
as it replaces my ugly home-grown bash script. However, it just picks
a seemingly random file in /etc/portage/package.keywords to put things
into. Is there a way to specify which file it writes
On Tue, 05 Jul 2011 10:58:57 -0500, Dale wrote:
Then again, that is yet another option to have to remember too. Jeez.
That's why we have EMERGE_DEFAULT_OPTS :)
--
Neil Bothwick
Top Oxymorons Number 46: Found missing
signature.asc
Description: PGP signature
Neil Bothwick wrote:
On Tue, 05 Jul 2011 10:58:57 -0500, Dale wrote:
Then again, that is yet another option to have to remember too. Jeez.
That's why we have EMERGE_DEFAULT_OPTS :)
Yea but I don't always want it to unmask packages either. If I was
going to let that be the
On Tue, 05 Jul 2011 15:43:36 -0500, Dale wrote:
Then again, that is yet another option to have to remember too.
Jeez.
That's why we have EMERGE_DEFAULT_OPTS :)
Yea but I don't always want it to unmask packages either. If I was
going to let that be the default,
I thought we were
Neil Bothwick wrote:
On Tue, 05 Jul 2011 15:43:36 -0500, Dale wrote:
Then again, that is yet another option to have to remember too.
Jeez.
That's why we have EMERGE_DEFAULT_OPTS :)
Yea but I don't always want it to unmask packages either. If I was
going to let that
10 matches
Mail list logo
