From: Marius Bakke <mbakke@fastmail.com>
To: Tanguy Le Carrour <tanguy@bioneland.org>,
Danny Milosavljevic <dannym@scratchpost.org>
Cc: Guix <guix-devel@gnu.org>
Subject: Re: Questions about packaging
Date: Fri, 18 Oct 2019 19:16:35 +0200 [thread overview]
Message-ID: <87y2xix9cc.fsf@devup.no> (raw)
In-Reply-To: <20191014075154.glbillit5hu7p6vb@rafflesia>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Hello Tanguy,
Tanguy Le Carrour <tanguy@bioneland.org> writes:
> In Guix, we have Pytest 4.4.2, but the latest release is 5.2.1.
> In that case, would it make sense to define a new "versionned" public
> variable for python-pytest? Would I create python-pytest5? Or would I
> rename python-pytest to python-pytest4 and add python-pytest for Pytest
> 5? In this later case, would I have to "fix" all the packages that were
> using python-pytest?!
Pytest has 4457 dependent packages and can thus only be changed on the
'core-updates' branch. So the recommended way is indeed to define a new
public 'python-pytest-5' variable, and add that as an input for the
packages that require 5.x.
On the next 'core-updates' cycle, Pytest 5 will then become the default,
and we will have to fix all packages that does not work with that
version :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-18 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 9:56 Questions about packaging Tanguy Le Carrour
2019-10-10 0:41 ` Danny Milosavljevic
2019-10-11 7:42 ` Tanguy Le Carrour
2019-10-12 10:41 ` Danny Milosavljevic
2019-10-12 10:49 ` Danny Milosavljevic
2019-10-14 7:53 ` Tanguy Le Carrour
2019-10-14 7:51 ` Tanguy Le Carrour
2019-10-18 17:16 ` Marius Bakke [this message]
2019-10-21 9:23 ` Tanguy Le Carrour
2019-10-21 9:34 ` Gábor Boskovits
2019-10-23 18:10 ` Marius Bakke
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=87y2xix9cc.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=tanguy@bioneland.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).