Douglas Pollock <[EMAIL PROTECTED]> writes:
[...]
> I'm wondering how these two different flavours -- integration builds and
> milestones -- might be matched with the ebuild naming scheme.
At first I thought of some kind of canonical form, but it looked
messy...
eclipse-sdk-2.1.2.0.2003.11.03
----- | ----------
| | |
release | build date
|
milestone
For example:
eclipse-sdk-2.1.1.0.2003.11.03
eclipse-sdk-2.1.2.0.2003.11.03
..
eclipse-sdk-3.0.0.1.2003.06.05 (milestones)
eclipse-sdk-3.0.0.2.2003.07.18
...
eclipse-sdk-3.0.0.0.2003.12.18 (integration)
But then there's some problems: milestones are fabricated to be zero
for release and integration builds in our mapping, and we also
fabricate an extra minor version column (3.0.0 gentoo cf. 3.0
eclipse).
Perhaps work with the slotting mechanism this way as an improvement
on that:
For SLOT="2"
eclipse-sdk-2.0
eclipse-sdk-2.0.1
eclipse-sdk-2.0.2
eclipse-sdk-2.1
For SLOT="3"
eclipse-sdk-3.0.1 (milestone 1)
eclipse-sdk-3.0.2 (milestone 2)
And finally, a (fabricated-ish??) SLOT="4"
eclipse-sdk-4.0.20031218 (integration from that date)
With slotting you'd want to ensure each could exist side-by-side
however.
Just an idea anyway.
Matt
--
Matthew Kennedy
Gentoo Linux Developer
--
[EMAIL PROTECTED] mailing list
