Re: [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.)

2021-09-01 Thread Carlo Zancanaro
On Wed, Sep 01 2021, Liliana Marie Prikler wrote: TL;DR: I'm generally in favor of branching emacs support packages off, even if origins are to be inherited. This is my preference, and there is precedent for this in Guix already. I know of emacs-protobuf-mode and emacs-erlang which are

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Liliana Marie Prikler
Am Mittwoch, den 01.09.2021, 19:48 + schrieb Jonathan McHugh: > September 1, 2021 8:35 PM, "Liliana Marie Prikler" < > leo.prik...@student.tugraz.at> wrote > > > Making our rando commit git versions look like such other distro > > versions does come at a disadvantage though, particularly when

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Jonathan McHugh
September 1, 2021 8:35 PM, "Liliana Marie Prikler" wrote > Making our rando commit git versions look like such other distro > versions does come at a disadvantage though, particularly when we look > at it through the lense of someone not used to Guix' versioning scheme. > Instead of telling us

I just got my pinephone.

2021-09-01 Thread Joshua Branson
Hey Guix! I just got my phinephone. It's currently running postmarketOS (1). I usually work nights two nights a week 10pm-6am (EST) Sunday night and Monday night. If a guix developer would like ssh access to it during those times, then please let me know. If I should use Mobian instead to

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

2021-09-01 Thread Sarah Morgensen
Hi, Maxime Devos writes: >> > have uses outside go-ethereum, so they can be re-used as dependencies of >> > new go packages, so over time, having to define many new packages when >> > importing >> > a go application should become less and less of a problem. >> > >> > (About version pinning:

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Liliana Marie Prikler
Am Mittwoch, den 01.09.2021, 18:39 +0200 schrieb Maxime Devos: > Liliana Marie Prikler schreef op wo 01-09-2021 om 15:33 [+0200]: > > Hi > > > > Am Dienstag, den 31.08.2021, 23:20 +0200 schrieb Maxime Devos: > > > Sarah Morgensen schreef op di 31-08-2021 om 12:57 [-0700]: > > > > Hello Guix, > >

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Xinglu Chen
On Wed, Sep 01 2021, Leo Famulari wrote: > On Wed, Sep 1, 2021, at 06:55, Xinglu Chen wrote: >> I never felt like including the commit id in the version of a package >> was useful; e.g., just seeing the first seven characters of the commit >> id doesn’t really tell me anything about the version.

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

2021-09-01 Thread Maxime Devos
Attila Lendvai schreef op wo 01-09-2021 om 14:29 [+]: > On Wednesday, September 1st, 2021 at 00:21, Maxime Devos > wrote: > > > Hi, > > > > Warning: I haven't actually ever touched a go package. Take my mail > > with a huge grain of salt. > > Much of this you've probably already heard at >

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Maxime Devos
Liliana Marie Prikler schreef op wo 01-09-2021 om 15:33 [+0200]: > Hi > > Am Dienstag, den 31.08.2021, 23:20 +0200 schrieb Maxime Devos: > > Sarah Morgensen schreef op di 31-08-2021 om 12:57 [-0700]: > > > Hello Guix, > > > > > > Currently, there are about 1500 packages defined like this: > > >

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Maxime Devos
> > (define-public sbcl-feeder > > (name "sbcl-feeder") > > (version (extended-version > > (base "1.0.0") > > (revision 1) > > (commit "b05f517d7729564575cc809e086c262646a94d34"))) > > (source > > (origin > > (method git-fetch) > > (uri

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Leo Famulari
On Wed, Sep 1, 2021, at 06:55, Xinglu Chen wrote: > I never felt like including the commit id in the version of a package > was useful; e.g., just seeing the first seven characters of the commit > id doesn’t really tell me anything about the version. I think it is > more useful to put the date of

Re: packaging go-ethereum, and ultimately bee (of ethswarm.org)

2021-09-01 Thread Attila Lendvai
On Wednesday, September 1st, 2021 at 00:21, Maxime Devos wrote: > Hi, > > Warning: I haven't actually ever touched a go package. Take my mail > with a huge grain of salt. > Much of this you've probably already heard at > https://logs.guix.gnu.org/guix/2021-08-31.log#024401. > > Attila Lendvai

Re: [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.)

2021-09-01 Thread zimoun
Hi, On Wed, 01 Sep 2021 at 14:05, Xinglu Chen wrote: > Cc’ing guix-devel to see what other people think before we start > breaking people’s setups. :-) I agree with this Andrew’s comment: P.S. I know that there are some emacs packages in Guix already, which doesn't use

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Liliana Marie Prikler
Hi Am Dienstag, den 31.08.2021, 23:20 +0200 schrieb Maxime Devos: > Sarah Morgensen schreef op di 31-08-2021 om 12:57 [-0700]: > > Hello Guix, > > > > Currently, there are about 1500 packages defined like this: > > > > --8<---cut here---start->8--- > >

Re: [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.)

2021-09-01 Thread Liliana Marie Prikler
Am Mittwoch, den 01.09.2021, 14:05 +0200 schrieb Xinglu Chen: > > IMO, notmuch package should not include Elisp stuff, at least I > > don't see use cases, where it can be useful, but see where it can > > be harmful. > > Should this apply to other packages that contains Elisp stuff too, or > is it

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Xinglu Chen
On Tue, Aug 31 2021, Maxime Devos wrote: > Sarah Morgensen schreef op di 31-08-2021 om 12:57 [-0700]: >> Hello Guix, >> >> Currently, there are about 1500 packages defined like this: >> >> --8<---cut here---start->8--- >> (define-public sbcl-feeder >> (let

Re: [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.)

2021-09-01 Thread Xinglu Chen
On Wed, Sep 01 2021, Andrew Tropin wrote: > On 2021-08-30 15:33, Xinglu Chen wrote: > >> On Mon, Aug 30 2021, Andrew Tropin wrote: >> Why would it be more consistent to make a separate package? Making a separate package is usually used for packaging a slightly different version of

Re: Can we find a better idiom for unversioned packages?

2021-09-01 Thread Xinglu Chen
On Tue, Aug 31 2021, Sarah Morgensen wrote: > Hello Guix, > > Currently, there are about 1500 packages defined like this: > > --8<---cut here---start->8--- > (define-public sbcl-feeder > (let ((commit "b05f517d7729564575cc809e086c262646a94d34") >

Re: Wireguard

2021-09-01 Thread Maxime Devos
crodges schreef op zo 29-08-2021 om 14:53 [-0700]: > Hello everyone, > > Let me start thanking you for developing such a interesting project in GNU > Guix. Also, I don't want to take up anyone's time, so you can just point to > documentation or other resource succinctly and I'll do my best. I'm