From: Cyprien Nicolas <gentoo@fulax.fr>
To: Pacho Ramos <pacho@gentoo.org>, gentoo-lisp@lists.gentoo.org
Cc: amynka@gentoo.org
Subject: [gentoo-lisp] Re: How to make dev & users happy about dev-scheme/guile
Date: Sun, 7 Jul 2019 11:48:06 +0200 [thread overview]
Message-ID: <608041fd-d5df-4cd6-d6c4-bbb4405d7e38@fulax.fr> (raw)
In-Reply-To: <3b334b81e98a14feca20dddba03cca8776e04687.camel@gentoo.org>
On 30/06/2019 10:11, Pacho Ramos wrote:
>
> Personally I would simply add a 2.2 slot for the new ebuild and start migrating
> deps to that one
>
> The same should be done for 1.8 slot:
> https://src.fedoraproject.org/rpms/compat-guile18
>
> For reverse deps the policy would be to use always the newest supported version
> , allowing the progressively drop the slots that become not needed
>
> To coordinate this I would open a bug in bugs.gentoo.org and provide the patches
> there (or as scheme@gentoo.org , that is the maintainer as listed in
> metadata.xml as I just checked, but I guess you don't need to resend all the
> mails as the only member of the project is amynka).
>
> Then, we can start adding the slotted ebuilds and checking reverse deps
>
I'm fine with that plan, I'll have to dig further about 1.8, as there
was a conflict with guilereadline libraries between 1.8 and 2.0.
I have a few issues to sort out with upstream first, then I'll open the
tracker bug, put patches and open a GitHub Pull Request as suggested by Amy.
Thanks for your advice.
prev parent reply other threads:[~2019-07-07 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 16:09 [gentoo-lisp] How to make dev & users happy about dev-scheme/guile Cyprien Nicolas
[not found] ` <28b7c2228475ab1fd17c8bdd0d39712e705e7e2b.camel@gentoo.org>
2019-06-22 13:38 ` [gentoo-lisp] " Cyprien Nicolas
[not found] ` <3b334b81e98a14feca20dddba03cca8776e04687.camel@gentoo.org>
2019-07-07 9:48 ` Cyprien Nicolas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=608041fd-d5df-4cd6-d6c4-bbb4405d7e38@fulax.fr \
--to=gentoo@fulax.fr \
--cc=amynka@gentoo.org \
--cc=gentoo-lisp@lists.gentoo.org \
--cc=pacho@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox