Date: Sat, 05 Apr 2008 20:55:25 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Maxim Khitrov <mkhitrov@gmail.com> Cc: "Philip M. Gollucci" <pgollucci@p6m7g8.com>, freebsd-ports@freebsd.org Subject: Re: FreeBSD Custom Package Server Message-ID: <47F7D92D.8060805@infracaninophile.co.uk> In-Reply-To: <26ddd1750804051234s67ba8b70l1276fe964e34ab62@mail.gmail.com> References: <26ddd1750804041811p4bb2c4f5tbab3f9659f88e8bb@mail.gmail.com> <47F7CBBD.4050107@p6m7g8.com> <26ddd1750804051234s67ba8b70l1276fe964e34ab62@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)
--------------enig43745DBFF53787E9D4666D31
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Maxim Khitrov wrote:
=20
> A request for new package should contain in itself all the relevant
> settings. If that means sending the make.conf file from the client to
> the server - fine. Have the build server adapt for each new request,
> build the requested port and dependencies, create the package(s), and
> remove the port from the local system. The client can then download
> the package, build server goes on to process the next request, and no
> disk space is wasted. Am I being a bit overambitious? :)
You'll need not just the data for the package you're going to build, but
the same data for all of the dependencies of that package, and you'll nee=
d
to install all of the dependencies in your build area. How are you going=
to handle dealing with OPTIONS screens, not just for the target package
but for its dependencies? Especially when changing the OPTIONS will likel=
y
change the dependency graph. Not an insurmountable problem, but not triv=
ial
either.
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
--------------enig43745DBFF53787E9D4666D31
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
iEYEAREIAAYFAkf32TIACgkQ8Mjk52CukIwz+ACfb6354f1SPwLtXGCpYUUUIquy
pUsAniwjhlb6yBIBDs+FeEdWSFFYWTGJ
=6twD
-----END PGP SIGNATURE-----
--------------enig43745DBFF53787E9D4666D31--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47F7D92D.8060805>