[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Naming (Re: Unified packages. )
On Mon, Aug 21, 2000 at 12:37:13PM -0400, Chris Coleman wrote:
> One of the new features is going to have to be a top level "make
> packages" that builds all the packages in the entire collection.
> Somehow we have to encode the OS, Release version, and Arch into the
> package. With a download directory structure, its fine to leave it out of
> the name. Without that, we should have an option to include the OS and
> arch in a way that can be easily stripped off by the package tools.
This presumes that we intend to not only provide a working common ports
tree, but also provide packages for each os/arch supported. Might I suggest
that this is abit forward for a beginning project? Think of the disk space.
Distfiles maybe, but packages for everybody and every arch?
Just a silly thought, but how about the 'official package distributions'
be done by each os .. and the 'bsdports' group or whatever we eventually
call it .. can focus on making sure things are uptodate and working ..
and not providing packages, which is imho an entirely separate effort
entirely .. unless we managed to do something akin to fat binaries, but that
would not be practical imho ;-)
> The packaging tools are going to be affected by this, so we might as well
> plan for it.
Not sure there are mods needed. Currently packages I build go into
/usr/ports/packages/i386/All/ with links from i386/net/ and i386/x11/ etc
as CATEGORY settings are found in their Makefile's. The path variable
to this could easily be extended to be packages/OpenBSD/2.7/i386/All with
little trouble. And you can change the name of the tarball, the package
doesn't always have to have the same name as the tarball. This is
how sslUSA27.tgz installs to ssl-2.7-USA .. perhaps this is OpenBSD
specific. I don't know.
Someone mentioned a global 'make package' target. I use this to build
all the OpenBSD packages (for testing only since I'm in the US) on my
machine today. If others dont have this, another item for what we bring
to the table.
Todd Fries .. firstname.lastname@example.org
To unsubscribe: send mail to <email@example.com>
with "unsubscribe bsdports" in the body of the message