unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: st: Mov to terminals.scm.
Date: Mon, 08 Aug 2016 19:14:25 -0400	[thread overview]
Message-ID: <87fuqeq2em.fsf@netris.org> (raw)
In-Reply-To: <874m6vc5mx.fsf@gnu.org> (Mathieu Lirzin's message of "Mon, 08 Aug 2016 23:28:22 +0200")

Mathieu Lirzin <mthl@gnu.org> writes:

> iyzsong@member.fsf.org (宋文武) writes:
>
>> ng0 <ng0@we.make.ritual.n0.is> writes:
>>
>>> Hi,
>>>
>>> I think it's pointless to have a suckless.scm which bundles all software
>>> which just happens to follow suckless ideology/goals or be hosted
>>> there.
>>> That's why I did not commit ii to suckless but to irc.scm, no one will
>>> look into suckless.scm when what they really are looking for is not
>>> $suckless but application xy.
>>> I try to unbundle and remove suckless.scm with the next patches.
>>
>> Well, it's difficult to choose the "right" category for packages.
>> For example, 'dmenu' shouldn't go to 'wm.scm', it has nothing to
>> do with window managers.
>>
>> When a project makes multiple softwares, I think it's easier to
>> put all of them in one project file, eg: gnome and freedesktop.
>
> So you are in favour of keeping (gnu packages suckless)?

Fwiw, I'm in favor of keeping suckless.scm, and rejecting these proposed
package moves.

     Mark

  reply	other threads:[~2016-08-08 23:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07 12:33 [PATCH] gnu: st: Mov to terminals.scm ng0
2016-08-07 12:38 ` ng0
2016-08-08 13:38   ` 宋文武
2016-08-08 21:28     ` Mathieu Lirzin
2016-08-08 23:14       ` Mark H Weaver [this message]
2016-08-12  8:28         ` ng0
2016-08-07 13:46 ` Mathieu Lirzin
2016-08-07 15:05   ` ng0
2016-08-07 15:52     ` Mathieu Lirzin
2016-08-08  7:52       ` ng0

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=87fuqeq2em.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=mthl@gnu.org \
    /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).