pkg_create

Clifton Royston cliftonr at lava.net
Tue Aug 19 14:58:41 PDT 2003


[Sorry for the lost references, I'm reading this in digest form.]

> Date: Tue, 19 Aug 2003 10:13:18 -0700 (PDT)
> From: Julian Elischer <julian at elischer.org>
> Subject: Re: pkg_create
> To: Adam Balogh <adam at vattnet.net>
> Cc: freebsd-hackers at freebsd.org
> Message-ID:
> 	<Pine.BSF.4.21.0308191011160.60598-100000 at InterJet.elischer.org>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> There weas no resolution though I discoverred that teh mechanism for the
> bug is that the "-C" argument is applied to tar immediatly
> that such a line is encounterred on teh arg list or the pascking list.
> 
> the answer would be to not put the "-C" arg on the 'tar' list until a
> file to save is actually encounterred.
> 
> I have not done that yet however.  (other fish to fry).
> On 19 Aug 2003, Adam Balogh wrote:
...
> > The original discussion. 
> >
> > http://lists.freebsd.org/pipermail/freebsd-hackers/2003-June/001673.html

  In switching back and forth between FreeBSD and OpenBSD for a
prototype system we're building, I've noticed that the OpenBSD ports
system works in the conceptually "correct" order for package creation
(or at any rate the preferable-to-me order.)

  It first creates a root-like subtree in the work directory, installs
the port to that pseudo-root tree, creates the package from that
directory and only then installs the package it has just created.  In
other words, in OpenBSD ports "make install" does a "make package" and
then pkg_adds it, whereas in FreeBSD ports "make package" does a "make
install" and then pkg_creates it.  IMHO the former is more flexible,
because it allows you to create a package on a system without
installing it, and then install it onto a different system.  (Or, for
instance, build a whole suite of packages in advance and then install
them at a later time.)

  Seems to me this must mean OpenBSD either fixed the pkg_create bug or
found an adequate work-around for it using this relative root
directory.  Possibly worth looking into how it's solved there?  I must
admit I haven't yet been able to bend my head around either set of
master makefiles to understand how they work or how the bug is dealt
with, but I thought I'd throw this tidbit out where it might reach
someone who understands the FreeBSD ports make system better than I do.

  -- Clifton

-- 
     Clifton Royston  --  LavaNet Systems Architect --  cliftonr at lava.net

Did you ever fly a kite in bed?  Did you ever walk with ten cats on your head?
  Did you ever milk this kind of cow?  Well we can do it.  We know how.
If you never did, you should.  These things are fun, and fun is good.
                                                                 -- Dr. Seuss


More information about the freebsd-hackers mailing list