all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Spliting a huge package
Date: Thu, 7 Feb 2019 15:34:06 +0100	[thread overview]
Message-ID: <10520f9b-d6d7-a5b5-fca4-8900c78c051c@crazy-compilers.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 935 bytes --]

Hi,

following up a discussion from the GNUne mailinglist about how to slice
the software, I would like to learn about the best practice of packaging
huge packages in guix.

Assume gnuet will be delivered a one big TGZ, inclusing base-libs,
core-services, additional-services, guis for services. For e.g.
RPM-based distros the TGZ would be build once and then sliced into
packages like

- gnunet(-core)
- gnunet-gns-proxy
- gnunet-fs
- gnunet-fs-gui
- gnunet-conversation
- gnunet-conversation-gtk

When packaging with guix, one way would be to create several output (fs,
fs-gui, etc.). This would require uses to install e.g. "gnunet:fs-gui"
which is, well, curious for users.

What is the intened way to solve this in guix?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-02-07 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 14:34 Hartmut Goebel [this message]
2019-02-07 19:14 ` Spliting a huge package ng0
2019-02-10 22:38 ` Ludovic Courtès

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=10520f9b-d6d7-a5b5-fca4-8900c78c051c@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@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 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.