On 07/05/15 18:53, Gordan Bobic wrote: > On 05/07/15 17:28, Jacco Ligthart wrote: >> - and after some closer inspection of the RPM trees this is incomplete >> as well. >> >> for the last Item, I guess you missed all folders starting with 'old' in >> my 7.1 tree. 'old' here meant not changed since alpha release. > > Oh, I see! I thought the old-* stuff was all replaced. I'll make sure > it's added.
one easy way to look at it would be: Konsole output repodiff -o http://ftp.redsleeve.org/pub/el7-devel/el7/7.1/ \ -n http://ftp.redsleeve.org/pub/el7/packages/base/ \ -a armv5tel --simple the 'branding' part was meant for items which had branding issues. IIRC this should now hold 4 different cases of <vendor>.pool.ntp.org (ntp, chrony, ipa and system-config-date), indexhtml and probably some items where I debranded the update and did not bother with the base RPM (firefox comes to mind). To me it looks a bit strange that we have now some redsleeve-* RPMS in there. It would be my choice to put redsleeve-* items in extras is there a reason to put mate-* into the base? it is also in epel. same goes probably for pv, unique and vte. we discussed earlier to split out our extras from those from upstream. Maybe this is easiest done by adding an extras tree at the same level as base and update, to hold the upstream extras. our extras can than stay where they are, as integral part of the base (as it should) upstream extras are (again doing from memory) python-* libev and ttembed Jacco
_______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
