From: Ricardo Wurmus <rekado@elephly.net>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Policy to remove obsolete packages
Date: Wed, 06 Feb 2019 23:32:38 +0100 [thread overview]
Message-ID: <87h8dgfszd.fsf@elephly.net> (raw)
In-Reply-To: <F37D2A0C-E9B2-4519-8076-755587520EFE@riseup.net>
swedebugia <swedebugia@riseup.net> writes:
> I like the idea of keeping it simple and now we tried the lumped
> modules approach. I don't like it so much to be honest.
>
> It comes with obvious drawbacks when the package per file grow and
> subcategorization have to be done.
>
> But is it efficient in guile to load hundreds of modules where all
> pull in more or less the same dependencies?
>
> If yes I think your idea is worthwhile Nils.
>
> We might have 3 repos: wip, core, extra
[…]
This is a tangent. This thread is about removing obsolete packages.
Let’s not discuss moving packages each to their own module here. This
has been discussed elsewhere and it’s a can of worms (which is fine if
you’re a bird, but not so good if you want to close the can again).
If you’re interested in playing with this you can do this in a local
branch and see how it behaves and what drawbacks it has. But I don’t
think it’s a good use of our time discussing it (again).
--
Ricardo
next prev parent reply other threads:[~2019-02-07 10:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 11:16 Policy to remove obsolete packages Björn Höfling
2019-02-04 11:51 ` Pjotr Prins
2019-02-04 18:06 ` Andreas Enge
2019-02-04 22:18 ` Leo Famulari
2019-02-04 23:47 ` zimoun
2019-02-05 10:24 ` Björn Höfling
2019-02-07 12:40 ` zimoun
2019-02-08 8:47 ` Björn Höfling
2019-02-04 22:52 ` Ludovic Courtès
2019-02-05 10:13 ` Björn Höfling
2019-02-05 21:31 ` ng0
2019-02-05 22:47 ` swedebugia
2019-02-05 23:52 ` ng0
2019-02-06 22:32 ` Ricardo Wurmus [this message]
2019-02-07 12:42 ` swedebugia
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=87h8dgfszd.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/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).