On 08/19/2015 10:49 AM, hasufell wrote: > On 08/19/2015 07:37 PM, Zac Medico wrote: >> On 08/19/2015 09:33 AM, hasufell wrote: >>> I don't want to start a lot of bikeshed, but I think this information is >>> practically useless. >>> >>> If there has been a problem with a commit, ask the developer about his >>> repoman version (which I believe was the reason for this, unless you >>> want me to add "Package-Manager: paludis-2.4.0" to every commit ;). >>> >>> Let's just remove it. >>> >> >> The intent is to leave a record of the version of repoman used, which >> leaves an audit trail in case there's a bug in some some version (or to >> detect if someone is using an ancient version). It can especially be >> useful when new repoman checks need to be added for new EAPI features. >> > > Why is it called "Package-Manager:" then?
Because repoman in bundled with portage, I guess. I suppose we could change it to something else. > And how often was that useful in practice? Well, there haven't been any EAPI bumps lately. However, in the time that follows an EAPI bump, it can be very useful if there are new dependency features that require new repoman checks. -- Thanks, Zac
