Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 May 2006 16:09:39 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        Howard Jones <howie@thingy.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: print-cdrom-packages.sh??
Message-ID:  <20060521200939.GA41613@xor.obsecurity.org>
In-Reply-To: <44686D93.3020701@thingy.com>
References:  <44686D93.3020701@thingy.com>

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

--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 15, 2006 at 01:01:23PM +0100, Howard Jones wrote:
> Moving on with my automated installs, I want to build some additional=20
> packages into the FTP area of my install server, which was seeded from=20
> the 6.1-RELEASE ISOs.
>=20
> The "FreeBSD Release Engineering for Third Party Software Packages"=20
> document on the FreeBSD website says that the release-building process=20
> uses a script called print-cdrom-packages.sh to produce the list of=20
> packages to build. However, my source tree doesn't have this script, and=
=20
> a look in CVS suggests that it's no longer in use, and hasn't been since=
=20
> March 2005 (Revision 1.71, Mon Mar 21 19:19:24 2005 UTC - Retire=20
> print-cdrom-packages.sh as it has been replaced.).
>=20
> Is there any current documentation for how the package building process=
=20
> is done? Or am I looking at the wrong URL?=20
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng-packages/artic=
le.html
>=20
> Ultimately, I'll want to rebuild all the packages, so just getting the=20
> few extras I need right now doesn't really help. I intend to use 'make=20
> release' to keep a 6_RELENG install with fairly current packages=20
> available for new servers, so I don't need to do so much rebuilding=20
> immediately after a fresh install.
>=20
> Thanks in advance for any pointers, or even any "don't do that, do this=
=20
> instead"-type advice.

There's now a python script somewhere in release/ that replaced it and
does a better job.  It should be easy to find, and once you have it
can you submit a PR requesting the article be updated?

Kris

--OgqxwSJOaUobr8KG
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEcMkDWry0BWjoQKURArGWAKCIxtpaO3GD68XfxjG1c/esyxcrXQCgmowQ
UjxGLdEhLXzXZ6N/9jFEKec=
=/F2f
-----END PGP SIGNATURE-----

--OgqxwSJOaUobr8KG--



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