"Michael W. Lucas" <[EMAIL PROTECTED]> writes:
> After a database headache caused by my own doofusity,
*shrug* what would that be? In doubt, kill /usr/ports/INDEX*db and
/var/db/pkg/pkgdb.db, run portsdb -u ; pkgdb -Fa and see what you get.
> A search of the mailing list archive doesn't seem to
Scot Hetzel:
>On 8/23/06, Helge Oldach <[EMAIL PROTECTED]> wrote:
>> .if ${.CURDIR:M*/mail/fetchmail}
>> .MAKEFLAGS: -DWITH_NTLM
>> .endif
>>
>> Note specifically the ".MAKEFLAGS" trick above that IMHO won't easily
>> work with portconf.
>>
>That will work with portconf, without using .MAKEFLAGS:
>
On 8/23/06, Helge Oldach <[EMAIL PROTECTED]> wrote:
Scot Hetzel:
>While the portmanager, portupgrade, and portmaster tools allow you to
>keep your specific port options in a file, they are incompatible with
>each other and when building directly from /usr/ports, as the port
>options in these sepe
On Wed, Aug 23, 2006 at 03:50:57PM +0200, Helge Oldach wrote:
> Hmm... What is wrong with directly amending /etc/make.conf with, for
> example:
Nothing's wrong with it -- but from my perspective, it's hardly
user-friendly. No, not everything should be user-friendly, but
something of this nature s
Scot Hetzel:
>While the portmanager, portupgrade, and portmaster tools allow you to
>keep your specific port options in a file, they are incompatible with
>each other and when building directly from /usr/ports, as the port
>options in these seperate files are not available to the other tools
>or to
I wanted to let some others respond to this post before I did, but now that
they have ...
Michael W. Lucas wrote:
> Hi,
>
> After a database headache caused by my own doofusity,
D'oh, I hate when that happens. :)
> A search of the mailing list archive doesn't seem to lead me to a
> clear succes
Michael W. Lucas wrote:
> Hi,
>
> After a database headache caused by my own doofusity, I've been
> contemplating switching from portupgrade. (Hey, it's been a few
> years, things could have changed.) Checking in /usr/ports/sysutils,
> it seems that we have a whole bunch of different tools -- po
While the portmanager, portupgrade, and portmaster tools allow you to
keep your specific port options in a file, they are incompatible with
each other and when building directly from /usr/ports, as the port
options in these seperate files are not available to the other tools
or to /usr/ports. Thi
On 8/22/06, Michael W. Lucas <[EMAIL PROTECTED]> wrote:
Hi,
After a database headache caused by my own doofusity, I've been
contemplating switching from portupgrade. (Hey, it's been a few
years, things could have changed.) Checking in /usr/ports/sysutils,
it seems that we have a whole bunch of
