From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: Nils Gillmann <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: Packaging Inferno
Date: Wed, 17 Oct 2018 19:35:07 +0200 [thread overview]
Message-ID: <87k1mgjx2s.fsf@GlaDOS.home> (raw)
In-Reply-To: <20181009175525.4ch3ml4qovjxiywg@abyayala> (Nils Gillmann's message of "Tue, 9 Oct 2018 17:55:25 +0000")
Hello Nils,
Nils Gillmann <ng0@n0.is> writes:
> Diego Nicola Barbato transcribed 12K bytes:
>> Hello,
>>
>> Thank you for your feedback.
>>
>> Nils Gillmann <ng0@n0.is> writes:
>>
>> > Ludovic Courtès transcribed 1.9K bytes:
>> >> Hello Diego,
>> >>
>> >> Diego Nicola Barbato <dnbarbato@posteo.de> skribis:
[...snip...]
>> >> > ;; build mk
>> >> > (invoke "./makemk.sh")
>> >>
>> >> It would be ideal if we had a separate package for ‘mk’ (I suppose it
>> >> can run on POSIX systems, right?).
>>
>> @Ludo: This is Plan 9's mk (their version of make), which, I believe,
>> can run on POSIX systems. Though, if we were to add mk to Guix, i would
>> rather package the one provided by Plan 9 from Userspace [7] since that
>> project seems to be more active than Inferno.
>>
>> > I can finish my mk package and send it in.
>> > My mk is the canonical set of mk files as used by bmake.
>> > Sources are from http://crufty.net/help/sjg/mk-files.htm
>> > and/or places linked from there.
>> >
>> > If this matches the mk mentioned here, I can create this patch.
>>
>> @Nils: Your mk package seems to be unrelated to Plan 9's mk.
>
> Aha! I have it in 9base, which I have also packaged. At least according
> to the README in the 9base/mk/ folder it should be compatible.
>
> Now I don't know if we want all of 9base... I would leave analyis of
> that to you. If 9base on its own does not work, I can extract mk or
> create a package which just builds mk and gets rid of the other files.
>
> https://git.suckless.org/9base
>
> I haven't checked but would assume that differences exist between
> 9base (altough it states plan9 + inferno os) and inferno os mk.
AFAICT it should be possible to build inferno using 9base's mk. In fact
I think 9base is better suited for this purpose than Plan 9 from
Userspace (plan9port), which was where I suggested we should get mk
from, since it is much smaller.
I can not tell from the source if it will be necessary to extract mk, so
I will try to build inferno using 9base's mk as soon as you send in your
patch and get back to you should I encounter any problems caused by one
of the other commands provided by 9base.
Thanks!
Diego
next prev parent reply other threads:[~2018-10-17 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 8:11 Packaging Inferno Diego Nicola Barbato
2018-10-07 9:49 ` Efraim Flashner
2018-10-11 13:30 ` Diego Nicola Barbato
2018-10-11 13:44 ` Efraim Flashner
2018-10-08 13:00 ` Ludovic Courtès
2018-10-08 13:47 ` Nils Gillmann
2018-10-09 17:09 ` Diego Nicola Barbato
2018-10-09 17:55 ` Nils Gillmann
2018-10-17 17:35 ` Diego Nicola Barbato [this message]
2018-10-16 12:03 ` Ludovic Courtès
2018-10-21 13:59 ` Diego Nicola Barbato
2018-10-24 12:58 ` 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=87k1mgjx2s.fsf@GlaDOS.home \
--to=dnbarbato@posteo.de \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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 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).