unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: csantosb@inventati.org, Guix Devel <guix-devel@gnu.org>
Subject: Re: [emacs]: snapshots against latest versions
Date: Wed, 13 Sep 2023 20:13:48 +0300	[thread overview]
Message-ID: <87cyymdmib.fsf@saitama.mail-host-address-is-not-set> (raw)
In-Reply-To: <874jjzztur.fsf@inventati.org>

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

Hi Cayetano!  Allow me to chime in, although I'm
green.

Cayetano Santos <csantosb@inventati.org>
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))

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]

      reply	other threads:[~2023-09-14 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  7:55 [emacs]: snapshots against latest versions Cayetano Santos
2023-09-13 17:13 ` Munyoki Kilyungi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cyymdmib.fsf@saitama.mail-host-address-is-not-set \
    --to=me@bonfacemunyoki.com \
    --cc=csantosb@inventati.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).