all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: guix-devel@gnu.org
Subject: Proposal: Separate the guix repo
Date: Sun, 16 Jan 2022 04:21:31 +0000	[thread overview]
Message-ID: <d0a0ea8f-f89c-96a9-07e2-d2742e151129@rixotstudio.cz> (raw)


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

Currently it's taking me 1~4 hours (depending on the system without
outsourcing the load on high performance system) to build the guix
repository in order to be able to test the contribution and contribute
as such i am proposing to take an inspiration from Exherbo Linux and
separate the repositories, see https://gitlab.exherbo.org/exherbo

I believe that this approach has multiple advantages:
1. Significantly lower resource requirements to make a contribution
2. Better management as issue tracking can be done per repository and
enable developers who are comfortable in specified programming language
to focus on contributions there
3. It saves resources for automation as language and workflow specific
automation can have more specific trigger thus saving processing resources.
4. Cleaner git history
5. Faster system deployment as the user can specify that they don't need
e.g. engineering packages on their system
6. Much cleaner code as the packages would be separat
ed to be less
overwhelming (to reduce the files with thousands lines)

--
Jacob Hrbek


[-- Attachment #1.2: publickey - kreyren@rixotstudio.cz - 1677db82.asc --]
[-- Type: application/pgp-keys, Size: 713 bytes --]

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

             reply	other threads:[~2022-01-16  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16  4:21 Jacob Hrbek [this message]
2022-01-16  8:30 ` Proposal: Separate the guix repo Ryan Prior
2022-01-16  8:48   ` Julien Lepiller

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=d0a0ea8f-f89c-96a9-07e2-d2742e151129@rixotstudio.cz \
    --to=kreyren@rixotstudio.cz \
    --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.