Ulrich Mueller:
>>>>>> On Sun, 27 Jul 2014, Martin Vaeth wrote:
>
>> Kent Fredric <kentfred...@gmail.com> wrote:
>>> -r1.1 weirdness feels like it may cause more problems than it solves.
>
>> So far, nobody pointed out any problem which would be caused by -r1.1.
>> Which is not surprising, since the idea is that -r1.1 cannot be
>> distinguished from -r2:
>> It is only a hint to the PM that he *may* shortcut certain phases when
>> updating from -r1.
>
> I wonder if it wouldn't be saner to leave our revision syntax
> untouched.
>
> Instead, one could introduce a variable INSTALL_VERSION that would
> default to ${PVR} but could be set to the version of a previous ebuild
> instead. The PM could compare it against INSTALL_VERSION in the VDB
> and skip build and installation if versions match.
>
> Advantages:
> - Support for the variable could be optional. PMs not supporting it
> would do a regular revbump instead.
> - One could even imagine USE-conditional syntax for the variable.
>
Aren't we putting a lot of trust in ebuild writers here? If any, I'd say
this should definitely be an optional feature for portage as well and
default to off.
The only time I would really consider using this would be for the very
few time-intensive packages I maintain like paraview, rstudio or
blender. For the rest, it's too much effort.
It will probably also cause confusion for comaintainers and
collaborators, especially when INSTALL_VERSION points to a version that
has already been removed.
