Date: 18 May 2005 18:45:22 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Tony Shadwick <tshadwick@goinet.com> Cc: Vizion <vizion@vizion.occoxmail.com> Subject: Re: GNU cp location Message-ID: <44br78i265.fsf@be-well.ilk.org> In-Reply-To: <20050518165729.J62516@mail.goinet.com> References: <200505181212.47900.vizion@vizion.occoxmail.com> <200505181332.31712.vizion@vizion.occoxmail.com> <44psvoi4ut.fsf@be-well.ilk.org> <20050518165729.J62516@mail.goinet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tony Shadwick <tshadwick@goinet.com> writes:
> Yeah, I've done this recently, it works beautifully, albeit a bit time
> consuming. I wish I could throw out there a big sign that says more
> or less:
>
> "cvsup your ports tree, install using portinstall"
>
> Rather than people constantly trying to build manually from
> tarball. :\
Well, the ports system doesn't seem to have the precise version that
the OP was building...
> That and teach people to put their build flags in
> /etc/make.conf so that portupgrade 'remembers' how you built it last
> time, like so:
>
> .if ${.CURDIR:M*/mail/cclient}
> WITH_SSL_AND_PLAINTEXT=yes
> .endif
>
> .if ${.CURDIR:M*/mail/imap-uw}
> WITH_SSL_AND_PLAINTEXT=yes
> .endif
>
> The tricks you learn over time though. :)
For most portupgrade users, I think I prefer to recommend configuring
the pkgtools.conf file for that purpose. But then it *only* works if
you're having portupgrade do the build.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44br78i265.fsf>