Date: Wed, 07 Jun 2006 11:55:31 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Kris Kennaway" <kris@obsecurity.org> Cc: Jiawei Ye <leafy7382@gmail.com>, freebsd-ports@freebsd.org, Sergey Matveychuk <sem@freebsd.org> Subject: Re: portupgrade ideas page Message-ID: <op.tasbytso9aq2h7@mezz.mezzweb.com> In-Reply-To: <20060607031732.GB12014@xor.obsecurity.org> References: <4485DBF5.3070705@FreeBSD.org> <20060606211113.GA7845@xor.obsecurity.org> <c21e92e20606061845g65e840eh1d64553d119e1b30@mail.gmail.com> <20060607021330.GA11189@xor.obsecurity.org> <c21e92e20606061919g6cf0bb6ct101c47be3af19dd5@mail.gmail.com> <20060607022741.GA11522@xor.obsecurity.org> <c21e92e20606061939x3d8796dahaf6df2ed73ef4164@mail.gmail.com> <20060607031732.GB12014@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 06 Jun 2006 22:17:32 -0500, Kris Kennaway <kris@obsecurity.org>
wrote:
> On Wed, Jun 07, 2006 at 10:39:50AM +0800, Jiawei Ye wrote:
>> On 6/7/06, Kris Kennaway <kris@obsecurity.org> wrote:
>> >> If all customizations are to be done in make.conf, what is the point
>> >> of MAKE_ARGS in pkgtools.conf?
>> >
>> >Flexibility, it's not supposed to be the primary means of customizing
>> >your ports, that's make.conf's job.
>> >
>> >Kris
>> Eh, not supposed to be? I have to admit that this idea of
>> "correctness" is new to me.
>
> It's "correct" in the sense of "this is the way it was designed to
> work". portupgrade relies on the INDEX for computing dependencies,
> and the INDEX is a ports collection construct that uses ports
> collection resources including make.conf.
The portupgrade always work without INDEX. My INDEX is empty and I never
need it.
# ls -l /usr/ports/INDEX.dummy
-rw-r--r-- 1 root wheel 0 May 20 2003 /usr/ports/INDEX.dummy
# make -V PORTS_INDEX
/usr/ports/INDEX.dummy
The portupgrade's pkgversion will not work without INDEX, but I prefer to
use pkg_version instead.
Cheers,
Mezz
>> I have been using portupgrade since it
>> came into the ports tree. One thing I like about the
>> portupgrade/portmanager style of managing ports make_args is that they
>> provide a very simple syntax for specifying per-port args.
>> '<portname>'=>'arg1 arg2.....' (portupgrade style)
>> <portname>|arg1 arg2 arg3| (portmanager style)
>>
>> Does make.conf provide such syntax? Last time I read from the ML, one
>> needs the {curdir} magic boiler plate for that. It is hard on the eyes
>> and reduces useful information on a 80x25 console IMHO.
>
> The latter.
>
> Kris
--
mezz7@cox.net - mezz@FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.tasbytso9aq2h7>