Date: Wed, 7 Jun 2006 10:39:50 +0800 From: "Jiawei Ye" <leafy7382@gmail.com> To: "Kris Kennaway" <kris@obsecurity.org> Cc: freebsd-ports@freebsd.org, Sergey Matveychuk <sem@freebsd.org> Subject: Re: portupgrade ideas page Message-ID: <c21e92e20606061939x3d8796dahaf6df2ed73ef4164@mail.gmail.com> In-Reply-To: <20060607022741.GA11522@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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.
Jiawei
--
"Without the userland, the kernel is useless."
--inspired by The Tao of Programming
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c21e92e20606061939x3d8796dahaf6df2ed73ef4164>