On Friday, June 22, 2012 at 5:22 AM, Dag Sverre Seljebotn wrote: > > What Bento does is have one metadata file for the source-package, and > another metadata file (manifest) for the built-package. The latter is > normally generated by the build process (but follows a standard > nevertheless). Then that manifest is used for installation (through > several available methods). > > >From what I understand, this dist.(yml|json|ini) would be replacing the mainfest not the bento.info then. When bento builds a package compatible with the proposed format it would instead of generating it's own manifest it would generate the dist.(yml|json|ini). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120622/ab751169/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4