Re: Fwd: Breaking up base (was: current state of the binup project)

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

[wrapping lines]

On Wed Oct 23, 2002 at 03:52:16AM -0700, Gerardo Enrique Paredes wrote:
> On Wed, Oct 23, 2002 at 02:12:04AM -0600, Gerardo Enrique Paredes Mancia =
wrote:
> >=20
> >=20
> > ----------  Forwarded Message  ----------
> >=20
> > Subject: Breaking up base (was: current state of the binup project)
> > Date: Tue, 22 Oct 2002 13:46:18 -0400
> > From: The Anarcat <[email protected]>
> > To: Murray Stokely <[email protected]>
> > Cc: GERARDO ENRIQUE PAREDES MANCIA <[email protected]>,=20
> > [email protected]
> >=20
> > On Sat Oct 19, 2002 at 10:54:17AM -0700, Murray Stokely wrote:
> > [...]
> >=20
> > > the same mechanism.  We were not interested in changing the package
> > > format, because other groups (i.e. libh / openpackages) are more
> > > focussed on that.  We were focussed on updates, delivery, and breaking
> > > up the base system into discrete components.
> >=20
> > Really? I've been dreaming about breaking up base for a long time
> > now. Have binup started any work in this direction?
> >=20
> > I have a "paper" I started writing that I've been thinking to send to
> > -arch for a while now, should it be sent here instead?
> >
> Well, maybe i am wrong, but for doing a binary update everythin is
> almost laid, at least that's how i am trying to make it, this is the
> general approach i am gonna take:
>=20
> - the client contact the server and ask to see if a profile is
> available, let the profile be FreeBSD-4.7-RELEASE then asks for a
> certain "distribution", let' the distribtuion be doc.
> - The client now request the doc.aa, doc.ab, doc.?? chunks from the
> server, the server get them from their location on disk and send
> them to the client using sendfile(2) as Murray suggested.
>=20
> - Happilly the client get the chunks then checksum them and follow a
> silimar approach to install them (i.e: cat doc.?? | tar --unlink
> -xpzf - -C ${DESTDIR:-/}) as the current sysintall binary update
> procedure does.
>=20
> As i said before, correct me if i am wrong but this an "It Works"
> way of doing it , but i may be wrong about this is the way the
> project wants to do it. Please correct me if i am wrong and expect
> patches by the next week.

Sure it works.

The point is that this could be improved, but not necessarly on the
binup side. The client/server protocol is interesting and should
provide a powerful tool.

But everything about the doc.* chunks and the client checksumming and
installing them is not part of binup. It's part of the package system.

My point is that binup should be package-system agnostic. I would have
a directory of "packages" (whatever the format) associated with
profiles, but wouldn't impose a file format.

A.

--=20
Stop the bombings.
Stop the murders.
Anti-war.

--ctP54qlpMx3WjD+/
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE9trhbttcWHAnWiGcRAkqGAJ9wCORF1y9MQQuEkjnIGxCCHIeTygCgkMOo
qOXbr8xCTHjGZ16wVR88wUQ=
=rCDF
-----END PGP SIGNATURE-----

--ctP54qlpMx3WjD+/--

To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-binup" in the body of the message