unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: jbranso@dismail.de
To: "Jonathan McHugh" <indieterminacy@libre.brussels>
Cc: "Edouard Klein" <edou@rdklein.fr>,
	"Patricio Martínez" <maxxcan@disroot.org>,
	help-guix@gnu.org
Subject: Re: package manager guix on Windows and OSX
Date: Fri, 25 Jun 2021 20:56:22 +0000	[thread overview]
Message-ID: <999d14a56998b787056467406ba6c9c2@dismail.de> (raw)
In-Reply-To: <87wnqh3kc3.fsf@libre.brussels>

June 25, 2021 1:53 PM, "Jonathan McHugh" <indieterminacy@libre.brussels> wrote:

> Hi Joshua,
> 
> A Guix-BSD hybrid would be delectable.
> 
> I consider the OpenBSD community to be excellent, not only for their
> prioritising a tight kernel and high levels of security standards but
> because they refuse to release updates until documentation such as
> manpages are comprehensively written.

That and their software is top notch! Linus called their developers
"masturbating monkeys", because of their obsessive pursuit of security!
hahaha. At every shutdown, the OpenBSD kernel is re-linked. It's the same
kernel when you reboot it, but the binary is re-ordered. That's amazing!

> This final point is something which the Guix community needs to
> improve - there is too much of a publish first - decribe later philosophy. As somebody still trying
> to fully master I get the feeling that
> their are things which will elude me until I get enough battle scars and
> my productivity will be hampered until I reach that sweet spot (or at
> least become more proficient/confident at just asking!)

My personal feeling is that GNU should adopt Org mode as their documentation 
standard.  It's slightly easier to use than texinfo.  Thought texinfo is 
pretty rad.  :)
 
> I should state that I consider the help-guix and devel-guix to be highly
> informative, friendly and professional. There should be greater
> expectations of contributors to explain their improved functionalities
> in advance. Additionally, I hold your individual support to be
> exemplary.

Well thanks!  I might mount that compliment on my wall!

> Additionally, while I understand that MIT is in many ways deficient
> compared to GPL licenses, if not pernicious and counterproductive I do
> empathise regarding why networking engineers may prefer having a licence
> which permits encapsulation more readily.

Well, what is interesting, is that the HyperbolaBSD developers intend to 
rewrite 20% of the BSD kernel and license the whole project GPL.  :)

What do you mean by:

> empathise regarding why networking engineers may prefer having a licence
> which permits encapsulation more readily.
 

> Joshua Branson <jbranso@dismail.de> writes:
> 
>> Edouard Klein <edou@rdklein.fr> writes:
> 
> To port Guix to another operating system such as BSD (including OSX),
> one would have to translate these calls.
> 
> For example, Guix is the only software I've actually encountered that
> can not run in SmartOS' emulation of Linux, because the system calls it
> uses are not implemented there.
> 
> I would love for Guix to be a Multi Kernel package manager (I mean it
> works on the Hurd also, but I have never encountered a Hurd user in real
> life). My dream would be to port Guix to Plan 9 ;-)
>> Why Plan 9? May I ask? And I do really like the Hurd, but I use the
>> dvorak keyboard layout. My understanding is that the Hurd does not
>> support variant keyboard layouts yet... :(
>> 
>> I actually think that the Guix developers may want to consider a port to
>> the OpenBSD kernel, provided that the Hyperbola developers get
>> HyperbolaBSD working. Though I guess the Debian guys sort of did
>> already. :)
>> 
>> https://www.hyperbola.info/news/announcing-hyperbolabsd-roadmap
> 
> --
> Jonathan McHugh
> indieterminacy@libre.brussels


  parent reply	other threads:[~2021-06-25 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 18:09 package manager guix on Windows and OSX Patricio Martínez
2021-06-24 19:07 ` jbranso
2021-06-25 12:36   ` Edouard Klein
2021-06-25 17:07     ` Joshua Branson
2021-06-25 17:50       ` Jonathan McHugh
2021-06-25 20:56       ` jbranso [this message]
2021-06-25 23:18       ` indieterminacy
2021-06-26  0:25       ` jbranso
2021-06-26  8:47       ` indieterminacy
2021-06-27 20:05       ` Edouard Klein
2021-06-29  2:21 ` maxxcan

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=999d14a56998b787056467406ba6c9c2@dismail.de \
    --to=jbranso@dismail.de \
    --cc=edou@rdklein.fr \
    --cc=help-guix@gnu.org \
    --cc=indieterminacy@libre.brussels \
    --cc=maxxcan@disroot.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.
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).