On Mon, Dec 19, 2005 at 01:45:04PM -0500, solar wrote: > > So right now I'll go ahead and add the pycrypto code to portage, but > > will not yet add the dep to any ebuild or change anything metadata.xml > > or ChangeLog related (according to Jason 2.0.54 is still away one or > > two weeks anyway). > > If you do that please set it as a blocker for the .54 release. > Reintroducing ChangeLog/metadata.xml to Manifests would be a undesired > regression. Nothing in the portage as of <=.53 make direct use of those > two files and there is no security value in bloating the digest format > with them. Thats why they were removed 2.0.51.21 > > Making the argument for maybe portage in the future will use them is > not valid as they are currently omited and we/I have been told before > by the portage team (ferringb & jstubbs iirc??) that portage itself > wont be doing any .xml parsing in it's core. IE So that means not today > nor tomorrow will anything need to depend on those files in order to > build. Stated otherwise in irc in regards to your metadata.xml patch- metadata.xml support will be core, although due to certain constraints it'll be optional intially.
At some point, we're going to have to push long desc into the cache; at that point, portage will be required to be xml aware (yay). ~harring
pgpwo2Ept53wk.pgp
Description: PGP signature
