On Sat, 3 Aug 2019 10:10:47 -0700, Ian Zimmerman wrote:
> > Do you know what tools those were?
>
> Sorry, I don't remember. I'll be sure to post here if I encounter the
> same kind of problem.
I've not had any problems wither, but at least one program complains if
/etc/portage/make.conf is a
On 2019-08-03 11:31, Dale wrote:
> Do you know what tools those were?
Sorry, I don't remember. I'll be sure to post here if I encounter the
same kind of problem.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply
Ian Zimmerman wrote:
> On 2019-08-03 07:56, Neil Bothwick wrote:
>
>> Hooray! They've changed the default locations to something more
>> sensible. Keeping data in /usr never made sense, I switched PORTDIR
>> to /var/portage years ago. Keeping tarballs inside the portage tree
>> made even less
On 2019-08-03 07:56, Neil Bothwick wrote:
> Hooray! They've changed the default locations to something more
> sensible. Keeping data in /usr never made sense, I switched PORTDIR
> to /var/portage years ago. Keeping tarballs inside the portage tree
> made even less sense.
I tried to do that some
On 03/08/2019 18:32, Walter Dnes wrote:
So far so good. The basic system is installed and booting. One
question... can I just set the "bindist" USE flag globally.
Usually you unset it globally. If you allow some of the packages to be
built with it, you're going to lose some functionality
5 matches
Mail list logo
