On 2015-06-01 19:00, Jacco Ligthart wrote:
On 06/01/15 13:59, Gordan Bobic wrote:
Jacco,

Is your final EL7 build process complete? For the release I need to sign all the packages and put together an updated redsleeve-release package.
That means adjusting the directory structures somewhat, and I think it
would be a good idea to instante a temporary goal post freeze before
doing that. :)

It mostly is. There are 8 packages still to do. 4 are waiting on the
redsleeve ntp pool (they are build, just waiting for the hostnames to
come through). And 4 are branding/logo's etc related. I saw that you did
one of them, which I'll put in there later today.

On the directory layout, It was quite obvious (to me) when I made it,
but I can see why it's not obvious to others :)

You misunderstood what I meant. It wasn't that it wasn't obvious, it was
that it needs:
1) Moving to a different path so that signed packages can go into the
/pub/el7/ path

2) Pruning out duplicates and unifying the repositories. Any objections
to merging the base and updates into a single large rolling repository?
I think that would provide for a cleaner setup. We can then have a separate updates repository to keep the metadata on it small, and periodically merge
the contents of it back into the base repository. It would mean the base
is mostly static (reduces the amount of re-downloading of the large
metadata) and keep the updates repository reasonably small most of the time.

So:
el7-base: Rolling everything, updated with contents of el7-update periodically

el7-update: The recently updated packages

el7-epel: Exactly what it says on the tin.

el7-extra: All the extra stuff that we found useful but either doesn't
exist at all in any of the above, or the version exceeds what is availble
in the other repositories.

el7-$device: Extra device specific repositories, e.g. custom kernels and
drivers for various devices.

Thoughts?

Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to