https://bugzilla.redhat.com/show_bug.cgi?id=1018523 --- Comment #6 from Matthew Miller <mattdm@xxxxxxxxxx> --- (In reply to Vincent Batts from comment #5) > (In reply to Matthew Miller from comment #4) > > BuildRequires: golang-github-coreos-go-systemd-devel > > Use the import paths: > > BuildRequires: golang('github.com/coreos/go-systemd') > > with the actual import paths needed. This way it will be safe guarded for > splitting out the libraries into subpackages. Sure, works for me. Can you put this in the packaging draft? https://fedoraproject.org/wiki/PackagingDrafts/Go However, there is a side-effect of doing it this way -- when looking for packages which build-require a certain library for security update, the import path will have to be used, which seems more error-prone. See the repoquery in the security section at the end of the draft... unless you can think of something more clever I think it may come down to a tradeoff of the safeguard you have in mind vs. making it easier to manage security problems.... Anyway the important note *here* is the requirement, however it is expressed. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review