Re: package definition question: referring to source files of another package?

2023-09-02 Thread Liliana Marie Prikler
Am Samstag, dem 02.09.2023 um 20:35 -0700 schrieb Andy Tai: > Hi, this is a question for writing package definition. > > In some scenarios package A may refer to source files in package B. > The question is,  > 1. How to reference source directory of package B from within > definition of package

package definition question: referring to source files of another package?

2023-09-02 Thread Andy Tai
Hi, this is a question for writing package definition. In some scenarios package A may refer to source files in package B. The question is, 1. How to reference source directory of package B from within definition of package A? 2. can we even assume sources of Package B is available? Normally if

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread Vagrant Cascadian
On 2023-09-03, Ricardo Wurmus wrote: > Maxim Cournoyer writes: > >> In the simplest case, it can be as simple as: >> >> $ ./pre-inst-env guix refresh -u some-package >> [build it, try it, fix if needed] >> $ ./etc/committer.scm >> $ git send-email >> >> Since it's a single patch, there's no

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread Csepp
wolf writes: > [[PGP Signed Part:Undecided]] > On 2023-09-02 21:08:12 +0200, Csepp wrote: >> >> paul writes: >> >> > Hello Giovanni, >> > >> > I get that you really don't find the web based workflow to bring >> > enough advantages to justify the migration, but first please >> > consider the

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread Ricardo Wurmus
Maxim Cournoyer writes: > In the simplest case, it can be as simple as: > > $ ./pre-inst-env guix refresh -u some-package > [build it, try it, fix if needed] > $ ./etc/committer.scm > $ git send-email > > Since it's a single patch, there's no jumping through hoops to create > the original

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread wolf
On 2023-09-02 21:08:12 +0200, Csepp wrote: > > paul writes: > > > Hello Giovanni, > > > > I get that you really don't find the web based workflow to bring enough > > advantages to justify the migration, but first please consider the picture > > that > > Katherine sent and that we are

Re: Relaxing the restrictions for store item names

2023-09-02 Thread Eidvilas Markevičius
So I've being trying to tackle this issue by myself somewhat [1], but very quickly got into a problem where, even when the restrictions inside the store-api.cc are gotten rid of, this strange error appears on an encounter of any non-ASCII character that I don't know how to deal with: $ guix

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread Csepp
paul writes: > Hello Giovanni, > > I get that you really don't find the web based workflow to bring enough > advantages to justify the migration, but first please consider the picture > that > Katherine sent and that we are evaluating the adequateness of the email > medium as a FOSS

Re: The package/inherit trap

2023-09-02 Thread Maxim Cournoyer
Hi Mark, Mark H Weaver writes: [...] > I don't have time to write the doc, but I can offer a few words here. > > The fundamental question that needs to be asked, to decide whether to > write (define DERIVED-PACKAGE (package/inherit BASE OVERRIDES ...)) or > (define DERIVED-PACKAGE (package

Mumi search broken? (was: Re: How can we decrease the cognitive overhead for contributors?)

2023-09-02 Thread Liliana Marie Prikler
Hi, Am Samstag, dem 02.09.2023 um 18:08 +0200 schrieb Csepp: > Mumi currently fails at its main function of being a search engine > for issues.  I can't even find my own messages with keyword searches, > because for some reason Mumi connects each words with a logical or > and doesn't rank search

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread Csepp
Giovanni Biscuolo writes: > [[PGP Signed Part:Undecided]] > Hello Katherine, > > thank you for having summarized (part of) this thread in a list of > actionable tasks > > now Someone™ have the chance to decrease the cognitive overhead for > contributors by _increasing_ her cognitive overhead

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread paul
Hello Giovanni, I get that you really don't find the web based workflow to bring enough advantages to justify the migration, but first please consider the picture that Katherine sent and that we are evaluating the adequateness of the email medium as a FOSS contribution management tool /over

Re: How can we decrease the cognitive overhead for contributors?

2023-09-02 Thread Giovanni Biscuolo
Hello Katherine, thank you for having summarized (part of) this thread in a list of actionable tasks now Someone™ have the chance to decrease the cognitive overhead for contributors by _increasing_ her cognitive overhead to sort out and complete each task as a general comment, it seems to me

Re: Opportunity For Guix: RFI Areas of long-term focus and Prioritization

2023-09-02 Thread Sarthak Shah
I second this, this could be something very good for Guix. We have a number of favorable features that could be desirable in a high-trust environment such as stability, seamless rollbacks, the ability to bootstrap completely from source etc. Regards, Sarthak. On Tue, Aug 29, 2023 at 8:15 AM