Hi,
> This definitely falls into the IDE tooling issue that I complained about
> a bunch of times. There seems to be a reality distortion field around
> Lisp that makes some users believe that s-expressions automatically lead
> to a good IDE experience. And yet, Java IDEs have had automatic
Katherine Cox-Buday writes:
> Summary: for people who don't contribute to Guix a lot, each
> contribution has
> very high cognitive overhead. Can we work to reduce that?
>
> Hey all,
>
> Contributing to Guix is currently pretty difficult for me. I'm a Mom with a
> full-time job, and anything
Hi,
Sorry if I came off a bit harsh in the initial reply :) I didn't intend
for it to read as a "ugh, how don't you understand this" sort of thing
but that's what it appeared to be looking at it later.
(Communication: It's Hard™)
Aaanyway
Jonas Møller writes:
> Interesting, Guix
Hello,
About 2–3 months ago, I got an initial prototype of Bacula working on GNU Guix.
I had the Bacula Director, two separate Storage Daemons and the Baculum web
interface running in a GNU Guix VM on my Synology NAS.
At some point, I would really love to upstream these changes, but it's quite
MSavoritias writes:
>> I don't think we should distribute packages that have non-ascii
>> characters in their names. Of course I don't know all keyboards that
>> exist out there, but I don't think you can find a programmer that
>> can't type an ascii character, or a guix user that can't at least
Hi,
At some point, I sympathize.
On Wed, 23 Aug 2023 at 10:25, Katherine Cox-Buday
wrote:
> I don't use the email-based patch workflow day-to-day, so this is
> another area where I spend a lot of time trying to make sure I'm doing
> things correctly.
I agree that Debbugs is not handy at
I guess that's true, but I very much doubt errors like this would come
up very often. Out of precaution, we could make guix lint issue us a
warning whenever a non-ASCII character is detected in a package name
or elsewhere. This would lower the chances of such oversights
occurring even more.
On
Hi,
On Tuesday, August 22nd, 2023 at 6:49 AM, Eidvilas Markevičius
wrote:
> Therefore, my proposal is to relax these limitations as much as
> possible (or at least somewhat) and to allow some more freedom when it
> comes to naming packages and other kinds of items in the store. We
> could, of
Hi Hilton,
Hilton Chain skribis:
> With the commit [1] made hours ago, I have been granted commit access
> to Guix repository.
>
> Currently, I'm maintaining packages I may use and those I've touched,
> and for now I have no specific plan to move on. This means I can have
> more time to go
Hi Maxim,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
[...]
>> Yes, the problem is machine-learning output comes up more and more
>> frequently.
>>
>> I agree we need to come up with a policy (I’m a bit torn on this and not
>> too sure what I’d put in there.) Maybe we should set up a
Hi,
Simon Tournier skribis:
> Somehow, I do not any difference with the package ’gnubg’ for example;
> well my opinion is expressed in this thread [1]:
Would you like to (co-)lead a working group (maybe with Nathan, maybe
with help from free software folks outside the project too) on this
Hi,
Distopico skribis:
>> Regarding customization, ‘--with-input’ and perhaps other transformation
>> options may correspond to your needs:
>>
>>
>> https://guix.gnu.org/manual/devel/en/html_node/Package-Transformation-Options.html
>>
>
> According with the docs, it will make rebuilt the
Hi,
On Tue, 22 Aug 2023 at 09:49, Eidvilas Markevičius
wrote:
> Therefore, my proposal is to relax these limitations as much as
> possible (or at least somewhat) and to allow some more freedom when it
> comes to naming packages and other kinds of items in the store. We
> could, of course,
Julien Lepiller writes:
> Le 24 août 2023 10:41:23 GMT+02:00, Msavoritias a
> écrit :
>>
>>What I am saying here is that:
>>Its easy to see from our very US centric tech culture why everybody
>>should just use ASCII because "This is how it is". But there is very
>>little reasons why we
Le 24 août 2023 10:41:23 GMT+02:00, Msavoritias a écrit :
>
>What I am saying here is that:
>Its easy to see from our very US centric tech culture why everybody
>should just use ASCII because "This is how it is". But there is very
>little reasons why we shouldn't strive to be more inclusive of
Interesting, Guix already has git/url-fetch, what is keeping Guix from simply
fetching a cargo project and then running `cargo build` in the fetched source
directory?
If the problem is that the build daemon is sandboxed and doesn't have internet
access, it is also feasible to have one stage of
Hi Katherine,
Katherine Cox-Buday writes:
> That last part is what I wanted to discuss, because
> that's the part
> that prevents me from contributing more than I do, and I think there are
> probably others whom are impacted by this.
Yes, I'd actually love contributing more to Guix; but even
What I am saying here is that:
Its easy to see from our very US centric tech culture why everybody
should just use ASCII because "This is how it is". But there is very
little reasons why we shouldn't strive to be more inclusive of all
cultures.
Especially since nowadays where we have tools like
Nguyễn Gia Phong writes:
> [[PGP Signed Part:Undecided]]
> On 2023-08-24 at 10:41+03:00, MSavoritias wrote:
>> Nguyễn Gia Phong writes:
>> > I think the distinction must be made here between Guix and GuixSD.
>> >
>> > The packaging software should support full localization,
>> > but the
On 2023-08-24 at 10:41+03:00, MSavoritias wrote:
> Nguyễn Gia Phong writes:
> > I think the distinction must be made here between Guix and GuixSD.
> >
> > The packaging software should support full localization,
> > but the distro should target the least common denominator.
>
> Depends what do we
Nguyễn Gia Phong writes:
> On 2023-08-24 at 10:16+03:00, MSavoritias wrote:
>> "(" writes:
>> > Eidvilas Markevičius writes:
>> > > with a name that contains non-Latin characters in it
>> > > (e.g., "Naršytuvas" by Raštija [2]).
>> >
>> > I think we should stick to ASCII characters in
On 2023-08-24 at 10:16+03:00, MSavoritias wrote:
> "(" writes:
> > Eidvilas Markevičius writes:
> > > with a name that contains non-Latin characters in it
> > > (e.g., "Naršytuvas" by Raštija [2]).
> >
> > I think we should stick to ASCII characters in package names,
> > since it's a bit
And some people don't have an english keyboard so its harder to type
english characters. Thats not a reason to exclude people in either
direction :)
I was not aware that its not possible to have Unicode characters in
store names but that is a bug to me at the very least (and exclusionary
of
Jonas Møller writes:
> Hi Guix! Why does cargo-build-system need #:cargo-inputs specified in the
> package definition? This seems like a
> big mistake for a couple of reasons.
>
> 1 It is completely redundant, it should match what is in Cargo.toml. I know
> `guix import crate` exists to
>
Eidvilas Markevičius writes:
> with a name that contains non-Latin characters in it (e.g.,
> "Naršytuvas" by Raštija [2]).
I think we should stick to ASCII characters in package names, since it's
a bit difficult to type `guix install naršytuvas` for those who don't
have keyboards with the 'š'
Katherine Cox-Buday writes:
> I signed up on Savannah with the intention of applying to be a committer.
> Savannah closed my account one or two days later due to inactivity.
That happened to me, too :|
> I can't ever seem to get the GNU style commit messages correct. I use the
>
26 matches
Mail list logo
