On 2019-03-29 16:16, Andreas Enge wrote:
> On Fri, Mar 29, 2019 at 03:02:00PM +0100, Tobias Geerinckx-Rice wrote:
>> I still think this change should be reverted
>
> I also think so.
Agreed, I remember having proposed and gotten a 1 name change through
the patch-review-process and that worked fin
On Fri, Mar 29, 2019 at 03:02:00PM +0100, Tobias Geerinckx-Rice wrote:
> I still think this change should be reverted
I also think so.
The wording in the naming guidelines is intentionally a bit vague;
the intention was definitely to take in general the tarball name, or maybe
if this does not fit
Hi Pierre!
Let's relax keep it friendly then! :) we are all having an
interesting
discussion and everyone brought up very good arguments.
Oh, I was annoyed by the luser/nerd dichotomy that's rampant
everywhere, not just (perhaps least of all) in Guix, not by any
person here! :-)
I still
On 2019-03-27 16:00, Ricardo Wurmus wrote:
>
> Pierre wrote:
>> Finally, as I mentioned above with the completion systems that we have,
>> we've got nothing to lose in having long names.
Reading the arguments of Ricardo I changed my mind and support keeping
the variable names short.
>
> swedebu
Pierre Neidhardt writes:
>> The package name is just an identifier for command line interaction
>> purposes.
>
> I don't see it this way. The package name is a global variable in the
> Guix project, and it bears a global semantic value. It's used as a
> public identifier that has to meaningfu
Ricardo Wurmus writes:
> Let’s fix that then and make it faster. (I think it’s pretty good
> already and it’s how I find packages, not by trying out names.)
The user experience I'm talking about is, well, the opposite: not to try
out names. But maybe this is hard to communicate over emails for
Pierre, hell, all,
Pierre Neidhardt wrote:
(Using Emacs-Guix.el, Helm, or the next GTK interface.)
Emacs? Helm? This ‘average user’ thing is a red herring.
I visited my mother today and she asked why my screen is always
black and white.
I admit to being irritated by this speculation in m
Hello,
Might be related to the subject (?) but would adding something like
keywords/tags to package definitions help? On Emacs, a package definition
like this can pop up:
ack is an available package.
>
> Status: Available from gnu -- Install
> Archive: gnu
> Version: 1.8
> Summar
swedebugia, Guix,
TL;DR: we're missing a field like ‘DISPLAY-NAME’, and all this is
just hacking around the bush.
swedebugia wrote:
Anyone else who have opinions on the matter of acronyms in names
where they can be avoided?
I share your aversion to acronyms and senseless abbreviation — I
j
Ricardo Wurmus writes:
> Completion should not be used as an excuse to use long package names.
> For one, not everyone is using Bash, so not everyone benefits from our
> Bash completions. (Some shells can reuse Bash completions but this does
> not invalidate the point.)
We could argue the other
Pierre wrote:
>Finally, as I mentioned above with the completion systems that we have,
>we've got nothing to lose in having long names.
swedebugia wrote:
> Good useability is important and cryptic acronyms are not something to
> expose to the user if possible to avoid IMO.
> Maybe this is where
Hello swedebugia,
swedebugia skribis:
> Good useability is important and cryptic acronyms are not something to expose
> to the user if possible to avoid IMO.
>
> Maybe this is where we need to discuss what our target audience is? Nerds
> only?
I think you’re jumping to the conclusions here.
Hi!
Pierre Neidhardt skribis:
> Ludovic Courtès writes:
>
>> Apologies if I missed a previous discussion on this topic, but… I’m
>> skeptical about the renames. I assume that the original names were
>> those commonly used in distributions, which in itself may be a good
>> reason to keep them.
Pierre Neidhardt skrev: (27 mars 2019 12:46:26 CET)
>Ludovic Courtès writes:
>
>> Apologies if I missed a previous discussion on this topic, but… I’m
>> skeptical about the renames. I assume that the original names were
>> those commonly used in distributions, which in itself may be a good
>> re
Ludovic Courtès writes:
> Apologies if I missed a previous discussion on this topic, but… I’m
> skeptical about the renames. I assume that the original names were
> those commonly used in distributions, which in itself may be a good
> reason to keep them.
Names may vary a lot across distributio
Hello,
guix-comm...@gnu.org skribis:
> commit 375cb94130b222535ad7c7e0fa0d212483407351
> Author: Pierre Neidhardt
> Date: Tue Mar 26 13:37:07 2019 +0100
>
> gnu: wesnoth: Rename package to the-battle-for-wesnoth.
> commit c91ed484d0b66d5639ba01f9ba301ff762d9170d
> Author: Pierre Neidhardt
16 matches
Mail list logo
