| 1 |
On Thu, Aug 13, 2015 at 1:13 PM, Ulrich Mueller <ulm@g.o> wrote: |
| 2 |
>>>>>> On Thu, 13 Aug 2015, Rich Freeman wrote: |
| 3 |
> |
| 4 |
>> On Thu, Aug 13, 2015 at 12:12 PM, Mike Frysinger <vapier@g.o> wrote: |
| 5 |
>>> delete it and be done |
| 6 |
> |
| 7 |
> +1 |
| 8 |
> |
| 9 |
>> When I asked a few days ago the arugment was made that it will be |
| 10 |
>> expanded when the ebuilds hit rsync, and then users can reference |
| 11 |
>> these when submitting bugs so that devs know what revision they're |
| 12 |
>> using/etc. It was stated that this was a highly-requested feature. |
| 13 |
> |
| 14 |
> If this is "a highly-requested feature" then some discussion or other |
| 15 |
> reference to it should exist in mailing lists. I can neither remember |
| 16 |
> nor can I find such a discussion. |
| 17 |
|
| 18 |
FYI, there has been one bug report about it since the git migration happened. |
| 19 |
|
| 20 |
https://bugs.gentoo.org/show_bug.cgi?id=557386 |
| 21 |
|
| 22 |
To quote the reporter: |
| 23 |
|
| 24 |
"Whilst many users may not care, this makes it much more difficult to |
| 25 |
tell whether a change has been made to an ebuild without a |
| 26 |
version-bump - and in my specific case, I maintain an overlay repo |
| 27 |
which attempts to track upstream, and this has removed my ability to |
| 28 |
(again, easily) tell if a minor update has been made to an ebuild I've |
| 29 |
overlaid." |
Archives