Zac Medico wrote:
> Zac Medico wrote:
>
>
>>>YoYo Siska wrote:
>>
>why should it handle USE flags in any way?
>it just tels portage not to emerge the dependencie, whatever they are (
>when added by use flags..)
>
>that means
>USE="alsa" emerge --nodeps mplayer
>would (
Zac Medico wrote:
>> YoYo Siska wrote:
>
why should it handle USE flags in any way?
it just tels portage not to emerge the dependencie, whatever they are (
when added by use flags..)
that means
USE="alsa" emerge --nodeps mplayer
would (try to) compile mplayer _wit
YoYo Siska wrote:
> Zac Medico wrote:
>
>>YoYo Siska wrote:
>>
>>
>>>Zac Medico wrote:
>>>
>>>
>>>
More drastic than my solution but it could be
necessary. I've seen USE="-*" more commonly but maybe
they're equivalent. I believe emerge --nodeps does
basically the same thing.
>>>
Zac Medico wrote:
> YoYo Siska wrote:
>
>>Zac Medico wrote:
>>
>>
>>>More drastic than my solution but it could be
>>>necessary. I've seen USE="-*" more commonly but maybe
>>>they're equivalent. I believe emerge --nodeps does
>>>basically the same thing.
>>
>>no
>>USE="-*" skips all optional dep
YoYo Siska wrote:
> Zac Medico wrote:
>
>>More drastic than my solution but it could be
>>necessary. I've seen USE="-*" more commonly but maybe
>>they're equivalent. I believe emerge --nodeps does
>>basically the same thing.
>
> no
> USE="-*" skips all optional dependencies (depending on a use
Zac Medico wrote:
>>afterwards that I could have accomplished the same
>>by:
>>
>>USE="*-" emerge -v perl
>>
>
>
> More drastic than my solution but it could be
> necessary. I've seen USE="-*" more commonly but maybe
> they're equivalent. I believe emerge --nodeps does
> basically the same thin
On Fri, 10 Jun 2005 20:51:20 -0700, Ted Ozolins wrote:
> I ran into the same glitch on a new system. The only way I was able to
> get around that was to blank out my USE= in /etc/make.conf. I realized
> afterwards that I could have accomplished the same by:
>
> USE="*-" emerge -v perl
They aren'
--- Colin <[EMAIL PROTECTED]> wrote:
> Now that I've been thinking about it for a while, if
> OpenSSH needs Perl,
> shouldn't Perl be built before OpenSSH? This seems
> like an ebuild bug
> to me.
>
openssh depends on autoconf which depends on perl.
Apparently you have autoconf but not per
Zac Medico wrote:
--- Colin <[EMAIL PROTECTED]> wrote:
I'm compiling my system (emerge -env system), but
when it gets down to
building OpenSSH, it fails, saying "You need Perl
5." Pretending and
checking the tree shows that Perl 5 will be emerged
later on during the
install. Attempting to
--- Ted Ozolins <[EMAIL PROTECTED]> wrote:
> Colin wrote:
>
> > I'm compiling my system (emerge -env system), but
> when it gets down to
> > building OpenSSH, it fails, saying "You need Perl
> 5." Pretending and
> > checking the tree shows that Perl 5 will be
> emerged later on during
> > the
Colin wrote:
> I'm compiling my system (emerge -env system), but when it gets down to
> building OpenSSH, it fails, saying "You need Perl 5." Pretending and
> checking the tree shows that Perl 5 will be emerged later on during
> the install. Attempting to "emerge -v perl" attempts to emerge
> sv
--- Colin <[EMAIL PROTECTED]> wrote:
> I'm compiling my system (emerge -env system), but
> when it gets down to
> building OpenSSH, it fails, saying "You need Perl
> 5." Pretending and
> checking the tree shows that Perl 5 will be emerged
> later on during the
> install. Attempting to "emer
12 matches
Mail list logo
