Date: Wed, 07 Jun 2006 13:14:30 +0400 From: Sergey Matveychuk <sem@FreeBSD.org> To: Jiawei Ye <leafy7382@gmail.com> Cc: freebsd-ports@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: portupgrade ideas page Message-ID: <448698F6.2050507@FreeBSD.org> In-Reply-To: <c21e92e20606061919g6cf0bb6ct101c47be3af19dd5@mail.gmail.com> References: <4485DBF5.3070705@FreeBSD.org> <20060606211113.GA7845@xor.obsecurity.org> <c21e92e20606061845g65e840eh1d64553d119e1b30@mail.gmail.com> <20060607021330.GA11189@xor.obsecurity.org> <c21e92e20606061919g6cf0bb6ct101c47be3af19dd5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jiawei Ye wrote: > I *know* that there are limitations in the base tools or what to > expect. sysutil/portmanager can do this well enough (correct > dependancy), that's why I *wish* portupgrade could do this too. It's a > wishlist right? You're right, it's a wish list. But it does not touch portupgrade directly. portupgrade tools does not build own INDEX (does it portmanager?), It use a ready one. It's possible to implement, but it's not a purpose to grow the tools up. Moreover, building own INDEX is a long time process. I think nobody likes if it'll be rebuild every time you refresh the ports tree. -- Dixi. Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448698F6.2050507>