Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 May 2010 10:30:13 -0700
From:      Julien Laffaye <kimelto@gmail.com>
To:        Andrew Brampton <brampton+freebsd@gmail.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: GSoC:Complete Package support in the pkg_install tools and  cleanup
Message-ID:  <v2ofee671621005041030j7eedf416o9e5b98dd16e72bac@mail.gmail.com>
In-Reply-To: <u2zd41814901005040315mb53c0a8ejd9baed87454af35c@mail.gmail.com>
References:  <i2jfee671621005031928m7672c08bk5f6f74cca2b50bad@mail.gmail.com> <u2zd41814901005040315mb53c0a8ejd9baed87454af35c@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 4, 2010 at 3:15 AM, Andrew Brampton
<brampton+freebsd@gmail.com> wrote:
>
> Hi Julien,
>
> Glad you got onto the GSoC programme. I'm curious, what benefit is a
> complete package over many individual ones?

Hi Andrew,

If you cant or dont want to use the remote feature of of pkg_add (ex.
your packages are built with non default options and you think its
overkill to setup a server to distribute them) then you make a
complete package. You only have to copy one file (say on an usb
device), which is less error prone than 150 files.
The global idea is to write a meta port which depends on the desired
ports, type `make complete-package`, copy the output file on the
machine to bootstrap, pkg_add /path/to/complete-pkg and voila!

Regards,
Julien



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