Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 05 Apr 2002 11:06:05 -0500 (EST)
From:      John Baldwin <jhb@FreeBSD.org>
To:        "David O'Brien" <obrien@FreeBSD.org>
Cc:        cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org
Subject:   Re: cvs commit: src/usr.sbin/sysinstall install.c installUpgrade
Message-ID:  <XFMail.20020405110605.jhb@FreeBSD.org>
In-Reply-To: <20020404194007.A83785@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 05-Apr-2002 David O'Brien wrote:
> On Thu, Apr 04, 2002 at 09:36:57AM -0500, John Baldwin wrote:
>> I think a better comparison might be if you think about some of our current
>> ports.  We have things like vim and vim-lite.  Imagine having a single vim
>> package (so you don't have to duplicate all the share data) whose install
>> script installs either the big vim binary or the smaller binary (both
>> binaries
>> are in the package, hence a "fat" package as I mentioned earlier) depending
>> on
>> if the system has X installed, user preference, etc.  Since we would only
>> need
>> 1 copy of stuff that is now duplicated, we could actually end up with a net
>> space gain as well as solving the problem of how to handle having 10
>> versions
>> of a package for all the various WITH/WITHOUT combinations.
> 
> You are impliying the reason we have vim and vim-lite the way we do (and
> ghostscript w/o X11 and with); is due to using tar vs. zip.  You are
> toally wrong.  We can easily do the same with pkg's today.  What IS
> missing is the makefile bits to build things the way you invision.  Just
> how would you create vim.zip ?

No.  You could achieve something similar like we do with xemacs by having
a vim-share package and then vim and vim-lite packages that just have the
binaries.  However, now you have 3 different packages with which to further
confuse the user.  The tar vs. zip thing has to do with zip having an index so
that all the metadata is collected in one place as I've explained earlier. 
They aren't just different compression formats they are very different archive
formats as well.  The reason we have different vim packages is due to the
limitations of our current package system and libh attempts to use a new design
that doesn't have the same limitations (though it does have some limitations,
and it does make package generation more difficult I'm afraid).

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20020405110605.jhb>