Fwd: Building newer releases from SVN

[Andreas Beckmann]

On 2016-07-24 23:17, Luca Boccassi wrote:
> I've just tested 367, and after adding conflicts+replaces in
> libglx0-glvnd-nvidia to libglx0-nvidia the upgrade is clean.

I only cared for renames of packages I had actually uploaded to
sid/experimental, but I'm not against providing a better upgrade
experience for users of SVN builds :-) Thanks!
Maybe we should use versions like 367.xx-1~svnYYYYMMDD in SVN to prevent
mixing packages from different snapshots. (That would work at least for
anything with a Depends: nvidia-alternative (= exactversion))

> I've committed it since we have now quite a few users building from SVN
> and at least one downstream distribution, SteamOS, so this will make
> life easier for them. SteamOS in particular released the 367.27 drivers
> from our branch a while ago.

:-)

> Also I've run a few things and all seems fine, both with glvnd's libGL
> and with Nvidia's.

Does switching work easily enough? Requires swapping packages. I don't
plan to integrate this in the nvidia-alternative/glx-alternatives
mechanism as an additional choice dimension (if it can be avoided).

> Also vulkaninfo output looks good, but I don't own
> any Vulkan game unfortunately so I cannot do more tests.

Would there be any such game available on steam?


My next planned steps are:
* wait for 352.79-10~bpo8+1 to enter backports
* upload 355/358/361 to sid with 12 hours gaps to allow package autobuilds
* upload 364/367 to experimental
(hopefully within July, expecting to have not much time at the beginning
of August)

* backport legacy-304xx/340xx

* continue working on gitification of nvidia-settings-* (66%done)


Andreas