unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed

From: Joshua Marshall <j.marshall@arroyo.io>
To: guix-devel@gnu.org
Subject: Feature requests
Date: Fri, 22 Mar 2019 13:47:19 -0400	[thread overview]
Message-ID: <CABDhO3CHXEhU2dCq1urujRfbVKKdaaynGRJ9MLHkPzeRWy+8KA@mail.gmail.com> (raw)

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

Hello all,

I was told in IRC to post my possibly unreasonable feature requests here.

I've been thinking more on what Guix might be able to do, and what would
make it more useful for a few of my past jobs.  I'd like to see it take on
the ability to have a per-installation target cgroup, network namespace,
and filesystem chroot settings set with defaults which are overridable at
invocation.  In this way, a user could install and use packages with
mutually incompatible dependencies (I talked about this with a few people
on IRC) like what happens with python.  If this kind of functionality were
added, it would largely supplant Docker, virtualenv, pip, poetry, apk,
pacman, and probably a few other tools at my company which are there just
to handle this kind of frailness.  From this, I could also see an entry
point to adding build module support to start to replace tools like Make,
CMake, Meson, Bazel, and so on.

These expand the scope of Guix quite a bit, but I think these are needed
for it to really feel logically complete.  Does all this make sense?

-- 



Please be advised that this email may contain confidential information. 
If you are not the intended recipient, please notify us by email by 
replying to the sender and delete this message. The sender disclaims that 
the content of this email constitutes an offer to enter into, or the 
acceptance of, any agreement; provided that the foregoing does not 
invalidate the binding effect of any digital or other electronic 
reproduction of a manual signature that is included in any attachment.


 
<https://twitter.com/arroyo_networks>   
<https://www.linkedin.com/company/arroyo-networks>   
<https://www.github.com/ArroyoNetworks>

[-- Attachment #2: Type: text/html, Size: 2783 bytes --]

next             reply	other threads:[~2019-03-22 18:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 17:47 Joshua Marshall [this message]
2019-03-22 22:30 ` Feature requests Julien Lepiller
2019-03-23 14:01   ` Joshua Marshall
2019-03-23 14:36     ` Julien Lepiller
2019-03-25  9:40 ` Giovanni Biscuolo
2019-03-25 17:38   ` Joshua Marshall
2019-03-26 17:19   ` Declarative containers Ludovic Courtès
2019-03-26 21:49     ` Giovanni Biscuolo
2019-03-27 11:18       ` 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

  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=CABDhO3CHXEhU2dCq1urujRfbVKKdaaynGRJ9MLHkPzeRWy+8KA@mail.gmail.com \
    --to=j.marshall@arroyo.io \
    --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

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).