On Tuesday 16 March 2010 04:02:08 pm Bill Nottingham wrote: > Dennis Gilmore ([email protected]) said: > > we will also announce our intention to branch. > > > > Every package that is not orphaned in EL-5 will be branched for EL-6. > > There needs to be some provision here for things included in EL-6 already > (I'm sure there will be some)
Sorry i was not clear enough that is whats planned to happen. People can opt out of branching and we will make sure anything in EL-6 is not branched. > > > for instance python-hashlib is in EL-5 to support stronger hashed > > metadata for the buildsystem. its part of newer pythons so my nobranch > > file will contain "Exists in newer python" this is just a historical > > something so if someone down the road questions why they can go and see > > > > We will give 2 weeks from announcement before we setup the cvs branches. > > this will let us make sure anything thats in EL-6 gets nobranch files > > we will be branching EL-6 branches from F-12 branches > > Can't there be some automation of this part - examine the EL-6 repo > for things that obsolete existing EPEL packages? Right, I was planning to do that. and put a nobranch file in the EL-5 branch that says its in EL-6
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
