Date: Sat, 05 Apr 2008 08:49:16 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Maxim Khitrov <mkhitrov@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD Custom Package Server Message-ID: <47F72EFC.3000808@infracaninophile.co.uk> In-Reply-To: <26ddd1750804041811p4bb2c4f5tbab3f9659f88e8bb@mail.gmail.com> References: <26ddd1750804041811p4bb2c4f5tbab3f9659f88e8bb@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig8DC7FB0F43A1B89D7A4D8809
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Maxim Khitrov wrote:
> I maintain several FreeBSD servers all of which currently use the
> ports system to install and update the needed software. I don't like
> using packages since I often need customizations made during the build
> process. For instance, my remote VPS has only 2 GB of disk space, so I
> need to build everything with the "-Os -s" optimization to make
> executables as small as possible. At the same time, some of the
> systems are also very limited in memory or processing power, so
> rebuilding certain ports (even with the help of ccache) is often a
> slow process.
>=20
> I'd like to help myself with a deployment of my own package server. It
> would work in a similar manner to the official FreeBSD servers, but
> there should be a dynamic component to it such that the client could
> request any number of customizations to the resulting packages.
> Basically, I don't want to sacrifice any of the flexibility of the
> ports system, only offload the actual build process to another
> dedicated machine.
I like this idea. I like it a lot. However I can see that it has the
potential to get very complicated and messy unless you have some clearly
thought-out architectural principles that you build the system around.
Personally, I'd take a leaf out of the package build cluster here: build
packages in a tinderbox style jail. Maintain as many different jail setu=
ps
as you have different environments to build packages for. 'environment'
meaning the unique combination of CPU architecture, OS version, compilati=
on
flags and port build options -- unless you've got a number of homogeneous=
systems that's quite likely to equate to maintaining an environment per
client host.
Even so, the capability to off-load package building onto a separate
-- presumably pretty high specification -- machine and to reduce the requ=
ired
down-time for upgrading the live servers; that would be more than suffici=
ent
justification for doing this.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--------------enig8DC7FB0F43A1B89D7A4D8809
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkf3LwEACgkQ8Mjk52CukIw07wCfeMZwQVypFCc0VK+Nq/DSDImw
7/oAn2qgVLOhcEMm249GKWawkiDB6rsO
=k/SP
-----END PGP SIGNATURE-----
--------------enig8DC7FB0F43A1B89D7A4D8809--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47F72EFC.3000808>