Hi Hartmut,
Hartmut Goebel writes:
> `guix refresh` always fetches the newest version of packages. This might
> not be desired in all cases. E.g. one might want to keep some still
> supported "major" upstream-version and not yet update to the next
> "major" version.
>
> Ludo suggested to add a
Am 19.06.2018 um 16:17 schrieb Marius Bakke:
> I'm not convinced that adding a property to some 80 packages is better
> than patching the importer. To me this problem seems very
> importer-specific (knowing what releases are considered LTS).
I disagree this is imported specific. Imagine we would
Hartmut Goebel writes:
> Am 29.05.2018 um 01:26 schrieb Marius Bakke:
>> Can we simply patch the KDE importer to stick with 5.12 for now?
>
> Not a good solution IMHO. For now I can also use "guix download"as a
> work-around This is not comfortable, but avoids having a forgotten
> "feature" in
Am 29.05.2018 um 01:26 schrieb Marius Bakke:
> Can we simply patch the KDE importer to stick with 5.12 for now?
Not a good solution IMHO. For now I can also use "guix download"as a
work-around This is not comfortable, but avoids having a forgotten
"feature" in the code.
--
Regards
Hartmut
Hartmut Goebel writes:
> `guix refresh` always fetches the newest version of packages. This might
> not be desired in all cases. E.g. one might want to keep some still
> supported "major" upstream-version and not yet update to the next
> "major" version.
>
> Ludo suggested to add a property in
`guix refresh` always fetches the newest version of packages. This might
not be desired in all cases. E.g. one might want to keep some still
supported "major" upstream-version and not yet update to the next
"major" version.
Ludo suggested to add a property in packages that would instruct
updaters
