Learn more about these different git repos.
Other Git URLs
It would make more sense for users since extra is following inheritance when building
emm... the extra info can be exposed by getBuildConfig with inheritance.
This issue is not problem now.
But should extra info with inheritance be able to be exposed by taginfo cmd? (and arches)
Metadata Update from @julian8628:
- Custom field Size adjusted to None
Metadata Update from @tkopecek:
- Issue set to the milestone: 1.23
I needed to dig into tag extra data and ended up writing this script the other day. The key thing I needed to know was "which tag was this extra value getting inherited from?"
After some discussion, it's probably better to incorporate that functionality into the core tool.
It might sense to show this date in taginfo, though it could potentially grow to be complex. We don't follow inheritance for other data displayed there (e.g. we don't print the full inheritance tree). Note that taginfo doesn't currently take an --inherit/--no-inherit option.
As we move forward with this, getBuildConfig is probably misnamed, or perhaps just the wrong call.
Metadata Update from @jcupova:
- Issue tagged with: testing-ready
Metadata Update from @mfilip:
- Issue tagged with: testing-done
Commit bfd3034 fixes this issue
Commit c2570f7 fixes this issue
Commit 878284c fixes this issue
Commit 2518e81 relates to this ticket
to comment on this ticket.