unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: 37642@debbugs.gnu.org
Subject: [bug#37642] [PATCH] gnu: Add filters
Date: Wed, 09 Oct 2019 15:14:52 +0200	[thread overview]
Message-ID: <87lftu9i2b.fsf@nckx> (raw)
In-Reply-To: <14cbe887a25f732826a1e920e2d0140dbce51893.camel@gmail.com>

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

Jesse,

Jesse Gibbons 写道:
> That review was a bit of a mess. Let's see if I can rephrase 
> what you want,
> in a human-friendly format (no emacs involved):

Yes, I'm so sorry.  It looked fine while writing; I'm not actually 
on crack.

>>      * gnu/packages/filters.scm: New file.
>>      * gnu/local.mk: Add it.
>>      * gnu/packages/cvassistant.scm (filters): New variable.
> Spot my "commit message template" remnants!
>
> You want me to put it into either games.scm or toys.scm, 
> preferrably
> toys.scm, for the sake of organization.

Yes.  File naming and package categorization are an impromptu 
mess.  Single-package files exist, most of them probably shouldn't 
*or* they should be the norm as in Nix.  I suspect the reason that 
Guix diverged was mainly technical: many things about Guix can 
(still) be explained by ‘Guile does a bad thing otherwise’.

>> I had previously started a discussion on the guix-devel list 
>> with a similar
> concern and was convinced that it is fine to have some packages 
> isolated in
> their own files. That's why I put rednotebook cv-assistant 
> isolated in their
> own sources.

Sure.  It's impossible to document the current scheme because it's 
self-contradictory.  ‘Feels wrong to nckx’ is no great argument 
but it's all you're going to get here.  Even the name ‘filter’ 
would only make sense in the context of this package (hey, gzip is 
a filter too…).

This has officially got to much attention now :-)

> However, since you asked, and there are two different files it
> would fit in, I will put filters in toys.scm. I'll leave it to 
> you to
> convince the others that packages like cmatrix, cowsay, 
> fortune-mod, and no-
> more-secrets should be moved to toys because they are not games.

As much as I ♥ irrelevant things, that would just be noise.

> Make sure these are indented when I add a new file.
> I guess indent-code.el doesn't look outside the package 
> definition...

Good point, I hadn't thought of that.  Must be how we subtly force 
you to switch to emacs.

> Use a patch instead or move this to the source's snippet so 
> kenny is removed
> from the raw source.

A patch would contain a ‘negative’ verbatim copy of the non-free 
code so isn't an option here.

>> +         #:tests? #f))
> clarify we have no tests suite

Yep.  Ideally that comment would be redundant because we'd never 
flat-out disable tests in packages that have them, but we do.

>> +The GNU project hosts a similar collection of filters, the GNU
>> talkfilters.  Due
>> +to copyright concerns and difficulty in communication between
>> maintainers, these
>> +collections have not been merged.")
> You want me to remove this.
> I think it's appropriate to say something about gnu talkfilters 
> and note
> that this is not the same package, given that filters and 
> talkfilters
> packages are often confused with each other on the internet,

OK.  I didn't know they were often confused.  Would it make sense 
to add it to GNU's, too?

> but I will remove the last sentence.

Great.  It's the one that bothered me.

>  If the comments go beyond 80 characters I will move the 
>  comments above the license.

For such whole-line comments you *would* use ‘;;’, start with a 
capital letter, and end with a full stop…

> indent-code.el missed these comments.

Sounds like indent-code.el needs love from someone who likes 
writing elisp.

> Am I missing anything?

Not that I'm aware of.  Sorry again for the beastly formatting of 
my original message.

Kind regards,

T G-R

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

  reply	other threads:[~2019-10-09 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  2:00 [bug#37642] [PATCH] gnu: Add filters Jesse Gibbons
2019-10-08 14:59 ` Tobias Geerinckx-Rice via Guix-patches via
2019-10-08 15:21   ` Tobias Geerinckx-Rice via Guix-patches via
2019-10-08 19:46   ` Jesse Gibbons
2019-10-09 13:14     ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2019-10-10  4:40       ` Jesse Gibbons
2019-10-21 18:43         ` Jesse Gibbons
2019-10-27  1:45         ` Jesse Gibbons
2019-10-28 19:41         ` bug#37642: " Tobias Geerinckx-Rice via Guix-patches via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lftu9i2b.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=37642@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).