From: "Gábor Boskovits" <boskovits@gmail.com>
To: John Soo <jsoo1@asu.edu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Adding a %desktop-packages
Date: Sat, 4 Apr 2020 08:48:03 +0200 [thread overview]
Message-ID: <CAE4v=ph+7cCB6GgqtX4r5q=ZuMt9MD5uYoLP-SG8YLWJ=OUZZw@mail.gmail.com> (raw)
In-Reply-To: <m2v9mg9k17.fsf@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
Hello,
John Soo <jsoo1@asu.edu> ezt írta (időpont: 2020. ápr. 4., Szo 2:23):
> Hi there,
>
> I am on board with providing some predefined lists of packages.
>
> I raised the idea of providing smaller lists of packages that might go
> well together instead of one large %desktop-packages. One reason to do
> this, for instance, might be to not make someone who wants to use btrfs
> always import the ext4 packages. Or not lock someone into using nettools
> if they are using iproute2, etc.
>
> Similarly, I think that many users, myself included, use a manifest file
> to manage user packages. It would help to have finer grained
> package lists so that the manifests could reuse them and not be
> requiring system basics along with it.
>
> What do you think?
>
This is more in line with my thoughts. Also, if we have some of these fine
grained lists, it would be easy to provide collections of these, so we can
do both things, but in a more useful way.
>
> - John
>
Best regards,
g_bor
>
[-- Attachment #2: Type: text/html, Size: 1765 bytes --]
next prev parent reply other threads:[~2020-04-04 6:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 22:03 Adding a %desktop-packages Jan
2020-04-04 0:22 ` John Soo
2020-04-04 6:48 ` Gábor Boskovits [this message]
2020-04-04 8:04 ` Brice Waegeneire
-- strict thread matches above, loose matches on Subject: below --
2020-04-02 17:18 Adding ‘rottlog-service-type’ to ‘%base-services’ Ludovic Courtès
2020-04-03 11:37 ` Adding a %desktop-packages Joshua Branson
2020-04-06 8:01 ` Ludovic Courtès
2020-04-06 9:14 ` Gábor Boskovits
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=ph+7cCB6GgqtX4r5q=ZuMt9MD5uYoLP-SG8YLWJ=OUZZw@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.