On Thu, Oct 03, 2019 at 09:37:31AM -0500, Chris Adams wrote: > Once upon a time, Daniel P. Berrangé <berrange@xxxxxxxxxx> said: > > Or just add some RPM metadata tags to record the upstream SCM type + URL + > > branch / release tag, etc. The user can thus easily find the upstream > > full commit logs corresponding to the pacakge. > > IMHO that is only good when the Fedora package is nothing but the > upstream code, built with defaults. As soon as Fedora needs to add a > patch and/or systemd unit(s), change options, etc., there should be a > Fedora changelog. I doesn't have to be mutually exclusive with RPM changelogs. I think having a record of upstream SCM would be useful regardless. Many times when submitting patches to Fedora packages, I've been told to send my patch to upstream instead....which means trying to figure out where that upstream is for this given RPM. 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
