all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Tai <atai@atai.org>
To: Nala Ginrut <mulei@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Third-parties are back to upstream
Date: Fri, 10 May 2024 13:00:33 -0700	[thread overview]
Message-ID: <CAJsg1E9grierOfso0We81GUO3UbCgUuRQL9eBG73dgLc-=YdeA@mail.gmail.com> (raw)
In-Reply-To: <87v83r8w6t.fsf@gnu.org>

Because Guix has no concept of package maintainers and anyone can send
a patch to update a package, please make sure after the next release
you check the pending patches for your package to do what you
suggested regrading the 3rd party directory and retaining the two .scm
files.  If I send the updated patch I will try to do what you
suggested.  Please do check then.

On Sun, May 5, 2024 at 8:18 PM Nala Ginrut <mulei@gnu.org> wrote:
>
>
> Hi Tai!
> It should be in the next release, but it's already in the vanilla code.
> In case anyone try to test the develop branch with Guix.
>
> Best regards.
>
>
> > On Sat, May 4, 2024 at 9:01 AM <guile-user-request@gnu.org> wrote:
> >>
> >> Message: 1
> >> Date: Sat, 04 May 2024 13:00:22 +0900
> >> From: Nala Ginrut <mulei@gnu.org>
> >> To: "artanis@gnu.org" <artanis@gnu.org>
> >> Hi folks!
> >> I've removed intergrated guile-redis & guile-json in Artanis, and tweaked the
> >> interfaces, so folks may install their prefered version from upstream.
> >>
> >> Artanis become more lightweight now.
> >> And this will also alleviate the pain of the packagers.


  reply	other threads:[~2024-05-10 20:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.63.1714838456.15685.guile-user@gnu.org>
2024-05-06  1:58 ` Third-parties are back to upstream Andy Tai
2024-05-06  3:18   ` Nala Ginrut
2024-05-10 20:00     ` Andy Tai [this message]
2024-05-11  1:41       ` Nala Ginrut
2024-12-02  9:00       ` Nala Ginrut
2024-05-04  4:00 Nala Ginrut

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='CAJsg1E9grierOfso0We81GUO3UbCgUuRQL9eBG73dgLc-=YdeA@mail.gmail.com' \
    --to=atai@atai.org \
    --cc=guix-devel@gnu.org \
    --cc=mulei@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.