Due to numerous occasions of b0rkerage in the bootstrap snapshots,
bootstrapping has failed. A selection of issues that come up:
- XXXX/YYYYY-p.q is the latest version in the snapshot, but this
version
has been removed, and its distfiles have become unavailable (e.g.
rsync-3.0.0_pre2)
- XXXX/YYYYY-p.q was added in the snapshot, but breaks several
packages
(e.g. gcc-4.3.0)
perhaps we need to keep older versions for bootstrap ?
Because bootstrapping is just the preparatory step to your Prefix
installation, it need not to be bleeding edge, and preferably it just
works, of course. Keep in mind that the snapshots are used for the
first `emerge system`, after that an emerge --sync is run and hence
the life tree is used for the final `emerge -e system`. The pre-sync
stage is the trickiest part, since it heavily relies on a correct
order
of things, correct dependendies and working packages. The post-sync
stage is slightly less dramatic, since in principle the Prefix
system is
already functional at that stage.
To aid the pre-sync stage, I am considering to switch to usign stable
keywords for the system packages *only*. That is, the bootstrap
process
is done with stable keywords, all other packages remain ~arch and
hence
a user has to add ~arch to ACCEPT_KEYWORDS after bootstrapping
finishes.
i would think it would be better to use stable and testing like
normal. i would like to try to keep stable here.
There is one thing that I don't quite like:
switching from arch to ~arch means after `emerge -e system` nearly any
system package needs to be updated, that is quite a shame
So the alternative is to switch from arch to ~arch in the post-sync
stage. Thoughts here?
Questioni is now how are we going to implement this, if we all agree
this is the way to go? Do we agree in the first place?
--
Fabian Groffen
Gentoo on a different level
--
[email protected] mailing list
--
[email protected] mailing list
