unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Kei Kebreau <kei@openmailbox.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26374-done@debbugs.gnu.org
Subject: bug#26374: [PATCH] gnu: Move dillo to web.scm.
Date: Mon, 10 Apr 2017 17:58:02 -0400	[thread overview]
Message-ID: <87zifo3oyd.fsf@openmailbox.org> (raw)
In-Reply-To: <874lxwfv6x.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 10 Apr 2017 11:50:14 +0200")

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

ludo@gnu.org (Ludovic Courtès) writes:

> Kei Kebreau <kei@openmailbox.org> skribis:
>
>> Marius Bakke <mbakke@fastmail.com> writes:
>>
>>> Kei Kebreau <kei@openmailbox.org> writes:
>>>
>>>> * gnu/packages/dillo.scm: Remove file and move dillo...
>>>> * gnu/packages/web.scm: ...here.
>>>> * gnu/local.mk: Remove reference to removed file.
>>>
>>> I think it would be good to have a "web-browsers.scm" to try and keep
>>> things organized; web.scm is already a kind of "kitchen sink" for
>>> anything web related. What do others think?
>>>
>>> There are a few other modules that could be moved into a
>>> web-browsers.scm as well.
>>
>> Splitting web.scm into more specific parts could be useful IMO.
>
> Introducing web-browsers.scm for a start sounds good to me.
>
> Ludo’.

I've opened a new bug (maybe I should have just submitted the new one
here...), so if this can be re-examined that would be great. :-)

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

      reply	other threads:[~2017-04-10 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 19:14 bug#26374: [PATCH] gnu: Move dillo to web.scm Kei Kebreau
2017-04-05 19:39 ` Marius Bakke
2017-04-05 23:50   ` Kei Kebreau
2017-04-10  9:50     ` Ludovic Courtès
2017-04-10 21:58       ` Kei Kebreau [this message]

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=87zifo3oyd.fsf@openmailbox.org \
    --to=kei@openmailbox.org \
    --cc=26374-done@debbugs.gnu.org \
    --cc=ludo@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).