Hi Cayetano! Allow me to chime in, although I'm
green.
Cayetano Santos
aliandika:
> Hi Guix,
>
> Following a recent patch to an snapshot of an emacs package
> (emacs-mastodon), where latest stable (tagged) release dates back from
> a long time, the question of whether to send patches for non stable
> (tagged) versions is pertinent or not.
>
> Of course, the answer is clear: we only package stable. Guix manual
> (22.4.3 Version Numbers) clearly states that "We usually package only
> the latest version of a given free software project ... Occasionally,
> we package snapshots of upstream’s version control system (VCS)
> instead of formal releases. This should remain exceptional.". Fine
> with that.
>
From my experience, this depends. In the python
system, updating some things can have ripple
effects that propagate to other packages, and
sometimes in a not so nice way. For packages that
have ripple effects, I find useful to package to
the latest version upto where things are stable.
Also, sometimes, a recent change can introduce a
security bug, so in such a case, unless a patch is
provided, I see no need to be in the latest
version.
[...]
--
(Life is like a pencil that will surely run out,
but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
(hkp://keys.openpgp.org))
signature.asc
Description: PGP signature