On Wed, Jan 29, 2020 at 09:26:43AM +0000, Richard W.M. Jones wrote: > On Tue, Jan 28, 2020 at 02:06:40PM -0500, Stephen John Smoogen wrote: > > My main concern is that we have been coming up with 'standard' > > proposals for 20 years and we can't seem to get more than any 4 > > maintainers to agree to what that means... even if they do the same > > work in Debian/SuSE/Arch etc. Too many idiosyncratic techniques which > > they use to keep themselves sane or working in whatever environments > > they have. > > > > At this point, I will take whatever we can standardize on even if it > > is clay tablets mailed to Babylon (ok maybe something a little less > > archaic) > > Likely we can get the GNU project involved here. > > A simple "METADATA" file in the top level of each project > containing the information we need in a format to be decided. > > If you think about it, we cannot even get the *name or version* of a > project mechanically at the moment, which is incredible really. AppStream metadata is probably the best upstream adopted metadata system that exists right now: https://www.freedesktop.org/software/appstream/docs/ It has wide adoption amongst desktop applications, since it is used to populate the software install tools used by various desktop environments, but it isn't restricted to just desktop apps. One caveat is that often the metadata file shipped in the tarball is not complete & is expanded by the build system. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
