There're a good reason I advocate delaying the split. We don't yet have
the deployed technology to make it trivial (SM dependencies), and it
make the workload larger for the person at the wrong side of the funnel
- Doug.

We can't afford it. But we will soon, and we need to be ready, by having
unload scripts.

As you say, it is useful to create and test an image "shrunk" to base,
what we can't afford yet is to make it a release deliverable, with an
update stream and so forth.

But it would really be useful for someone to create an informal script
as you describe, to make it easier for people to test out the "core as
it will be".

Daniel

Cees de Groot <cg at cdegroot.com> wrote:
> 
> --Boundary_(ID_EOXSbL0wYYJhuoijNZKz8g)
> Content-type: multipart/signed; boundary="=-oAL+rrcwPO0998acsUAT";
>  protocol="application/pgp-signature"; micalg=pgp-sha1
> 
> 
> --=-oAL+rrcwPO0998acsUAT
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> On Sat, 2003-03-08 at 13:16, Daniel Vainsencher wrote:
> > While making the actual split into kernel/core/base will have to wait a
> > little until we have dependencies, we can start reviewing the existing
> > removal scripts now, that's the real measure of our progress.
> >=20
> I agree with your description of what needs to be done. However, I think
> it is useful to start applying these removal scripts to a 'core' image
> right away. The script that moves core -> base will be small, and it is
> quite feasible to keep it as a single manual script for the coming time.
> By the time that gets unfeasible, we'll have a largish script containing
> a lot of stuff we learnt about how to load a number of unrelated
> packages. This will provide valuable input to what is needed in the area
> of dependency mechanisms, so that when refactoring the script, we'll
> land at a) practical dependencies, and b) have a mini-package that
> brings core->base ideally just by listing dependencies).
> 
> Summary: removal/replacement pairs that have gotten the necessary
> reviews are immediately applied to the core/base split, by removing the
> package from 'core' and doing an appropriate update of the (monolithic)
> core->base script.
> 
> 
> 
> --=-oAL+rrcwPO0998acsUAT
> Content-Type: application/pgp-signature; name=signature.asc
> Content-Description: This is a digitally signed message part
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> 
> iD8DBQA+afpy8wOTf+CYnosRAuhZAKCBKi5UguxHDxFU9yRR7qYMuCVU6gCfYHxj
> gL8QvLq/6/E9ZdyS65Rwpb8=
> =fbW3
> -----END PGP SIGNATURE-----
> 
> --=-oAL+rrcwPO0998acsUAT--
> 
> 
> --Boundary_(ID_EOXSbL0wYYJhuoijNZKz8g)
> MIME-version: 1.0
> Content-type: text/plain; charset=us-ascii
> Content-transfer-encoding: 7BIT
> 
> 
> 
> --Boundary_(ID_EOXSbL0wYYJhuoijNZKz8g)--