tly state how @cwd should operate, but currently the directory
> >must exist for pkg_create to run properly.
> >
> >This is extremely annoying because build machines *must* create the
> >final directory structure of the target install before the package can
> >be create
Brenden Grace wrote:
In this thread:
http://lists.freebsd.org/pipermail/freebsd-hackers/2003-June/001673.html
some people seem to think that @cwd is broken. The man pages do not
explicitly state how @cwd should operate, but currently the directory
must exist for pkg_create to run properly.
This is
In this thread:
http://lists.freebsd.org/pipermail/freebsd-hackers/2003-June/001673.html
some people seem to think that @cwd is broken. The man pages do not
explicitly state how @cwd should operate, but currently the directory
must exist for pkg_create to run properly.
This is extremely
Adam Balogh wrote:
On Wed, 2003-08-20 at 07:21, Sergey Matveychuk wrote:
Adam Balogh wrote:
Hello,
Has anyone found a solution for the pkg_create problem
mentioned here in June?
I'm planing to hack pkg_install with other reasons.
So, I can take a look on this.
Sem.
That would inde
Adam Balogh wrote:
Hello,
Has anyone found a solution for the pkg_create problem
mentioned here in June?
I'm planing to hack pkg_install with other reasons.
So, I can take a look on this.
Sem.
___
[EMAIL PROTECTED] mailing list
[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 <[EMAIL PROTECTED]>
> Subject: Re: pkg_create
> To: Adam Balogh <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Message-ID:
&g
til 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:
> Hello,
> Has anyone found a solution for the pkg_create problem
> mentioned here in June?
>
> The original discussion.
> >
> http:/
Hello,
Has anyone found a solution for the pkg_create problem
mentioned here in June?
The original discussion.
>
http://lists.freebsd.org/pipermail/freebsd-hackers/2003-June/001673.html
Cheers, Adam
___
[EMAIL PROTECTED] mailing list
h
On Fri, Jul 04, 2003 at 11:38:01AM -0700, Tim Kientzle wrote:
> * Remove the need to install a package before
> creating the package file. In particular, using this library,
> you can separate the filename written into the
> library from the file used as a source of data.
Yes please! Where
ng to use a separate 'tar'
program. The attached is a functional alpha of "libtarfile", which
provides a pretty clean API for building and reading tar archives (complete
with gzip or bzip2 compression). In particular, this could be
incorporated into pkg_create to address bot
On Fri, 27 Jun 2003, John Baldwin wrote:
>
> On 25-Jun-2003 Kris Kennaway wrote:
> > On Tue, Jun 24, 2003 at 05:21:14PM -0700, Julian Elischer wrote:
> >>
> >> I'm trying to make a package..
> >> according to the man page for pkg_create:
> >
On 25-Jun-2003 Kris Kennaway wrote:
> On Tue, Jun 24, 2003 at 05:21:14PM -0700, Julian Elischer wrote:
>>
>> I'm trying to make a package..
>> according to the man page for pkg_create:
>
> Look into the ports collections for thousands of examples of how to
>
On Thu, 26 Jun 2003, Dwayne MacKinnon wrote:
> Julian Elischer wrote:
> > Alternatively, the man page hints that
> > a 'srcdir' would stop a following 'cwd' from having effect in the create
> > phase.
>
> Just wanted to mention that order is extremely important with package
> creation. If you
Arrgh. Forget what I just wrote about a @dstdir option. My brain
shortcircuited and I believed it actually existed.
Cheers,
DMK
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
Julian Elischer wrote:
Alternatively, the man page hints that
a 'srcdir' would stop a following 'cwd' from having effect in the create
phase.
Just wanted to mention that order is extremely important with package
creation. If you have @cwd /foo/bar; @srcdir /bar/foo your files will be
picked up f
7;ve found, pain in the neck that it is, is to create
> the destination directories on the source box. That keeps pkg_create
> happy, and the proper files are still picked up from the where they're
> specified by SRCDIR.
>
> I meant to raise this a long time ago, but I go
the source box. That keeps pkg_create
happy, and the proper files are still picked up from the where they're
specified by SRCDIR.
I meant to raise this a long time ago, but I got busy, my package
creation box was set up so that pkg_create didn't complain, and out of
sight = out of
On Tue, 24 Jun 2003, Kris Kennaway wrote:
> On Tue, Jun 24, 2003 at 05:21:14PM -0700, Julian Elischer wrote:
> >
> > I'm trying to make a package..
> > according to the man page for pkg_create:
>
> Look into the ports collections for thousands of examples of
On Tue, Jun 24, 2003 at 05:21:14PM -0700, Julian Elischer wrote:
>
> I'm trying to make a package..
> according to the man page for pkg_create:
Look into the ports collections for thousands of examples of how to
create packages.
Kris
pgp0.pgp
Description: PGP signature
I'm trying to make a package..
according to the man page for pkg_create:
-s srcdir
srcdir will override the value of @cwd during package
creation.
-p prefix
Set prefix as the initial directory ``base'' to start
from in
Julian Elischer wrote:
>
> I need to take a directory of 'stuff'
> which includes a script install.sh
> and make it into a package..
> I have had some success but it's not quite right..
>
> What I'd like to make it do is:
> unpack the 'stuff' into a temporary directory somewhere.
> run the i
I need to take a directory of 'stuff'
which includes a script install.sh
and make it into a package..
I have had some success but it's not quite right..
What I'd like to make it do is:
unpack the 'stuff' into a temporary directory somewhere.
run the install script
delete the install direc
22 matches
Mail list logo
