all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: "Oleg Pykhalov" <go.wigust@gmail.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: How to install prerelease package versions (particularly Emacs)
Date: Tue, 27 Mar 2018 19:46:47 +0200	[thread overview]
Message-ID: <87muyth0mw.fsf@fastmail.com> (raw)
In-Reply-To: <87k1txedot.fsf@gmail.com>

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

Oleg Pykhalov <go.wigust@gmail.com> writes:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Pierre Neidhardt <ambrevar@gmail.com> skribis:
>>
>>> Considering the importance of Emacs in this community, I think it would
>>> make sense to provide a cutting-edge version.
>>
>> Do you mean a snapshot of the ‘master’ branch?
>>
>> We don’t do that usually, and I would instead suggest using
>> ‘--with-source’ for people who would like that.
>>
>> What do people think?
>
> In case of ‘emacs’ package recipe, ‘--with-source’ doesn't work for a
> snapshot of the ‘master’ branch.
>
> To build the ‘master’ branch you need to write a new package recipe.  I
> think it's not acceptable for a non-contributor in Guix.  WDYT?

This sounds like a job for the mythical "channel" facility.  In the mean
time, sharing package recipes for sticking in GUIX_PACKAGE_PATH like you
did upthread seems like a reasonable workaround.

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

  reply	other threads:[~2018-03-27 17:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  0:00 How to install prerelease package versions (particularly Emacs) Jorge
2018-03-03 10:24 ` Oleg Pykhalov
2018-03-19  4:13   ` Chris Marusich
2018-03-26 18:42     ` Pierre Neidhardt
2018-03-27  9:51       ` Ludovic Courtès
2018-03-27 12:24         ` Clément Lassieur
2018-03-27 15:33         ` Oleg Pykhalov
2018-03-27 17:46           ` Marius Bakke [this message]
2018-03-27 20:57           ` Ludovic Courtès
2018-03-28  7:12             ` Oleg Pykhalov
2018-03-30  7:06               ` Pierre Neidhardt
2018-03-30 12:13                 ` Mathieu Lirzin
2018-03-30 12:19                   ` Pierre Neidhardt
2018-03-30 13:08                     ` Mathieu Lirzin
2018-04-11 15:53                       ` Pierre Neidhardt
2018-04-12  8:29                         ` Chris Marusich
2018-04-12  9:12                           ` Pierre Neidhardt
2018-04-12 12:57                             ` Ricardo Wurmus
2018-04-12 13:21                               ` Pierre Neidhardt
2018-04-13  5:27                             ` Chris Marusich
2018-04-13  5:57                         ` Carlo Zancanaro
2018-04-01 14:09                 ` Oleg Pykhalov
2018-04-11 16:00                   ` Pierre Neidhardt
2018-04-12  8:28                     ` Chris Marusich
2018-04-12  8:32                       ` Pierre Neidhardt
2018-04-11 15:57               ` Pierre Neidhardt
2018-04-12  6:06                 ` Pierre Neidhardt
2018-04-05 15:53       ` Jorge
2018-04-05 19:36         ` Pierre Neidhardt
2018-03-03 13:46 ` Jorge

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=87muyth0mw.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=go.wigust@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@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.