From: Joshua Branson <jbranso@dismail.de>
To: help-guix@gnu.org
Subject: Re: jfs, jfsutils?
Date: Fri, 13 Dec 2019 09:31:53 -0500 [thread overview]
Message-ID: <86mubwi9eu.fsf@dismail.de> (raw)
In-Reply-To: <4454c84b-fa97-df27-d5d5-7e7a8643f8ef@gmail.com> (Michael Zucchi's message of "Thu, 12 Dec 2019 13:48:00 +1030")
Michael Zucchi <notzed@gmail.com> writes:
> Hi Tobias,
>
> On 12/12/19 12:11 pm, Tobias Geerinckx-Rice wrote:
>> Michael & me,
>>
>> Tobias Geerinckx-Rice 写道：
>>> - jfsutils needs to be packaged for Guix
>>
>> I wrote a quick but working package[0].
>>
>>> - and a static fsck added to the initramfs
>>
>> I didn't have time for this yet.
>>
>
> Ok so it seems you're half done already, but I've been plodding away
> (and didn't check my email on my old computer) and have both building.
>
> I'm not really sure where to put it or how to compile each part (it
> just build jfsutils, not jfs_fsck/static) and I used the slackware
> patches, but attached is what i have at the moment. I used jfs_fsck
> for the static fsck because that's the default name but it could be
> fsck.jfs.
>
> I started with a definitions of e2fsprogs and it's related functions
> from a linux.scm i found in /gnu/store and based it on that.
>
> I've a number of built package 'attempts' building up - should I just
> run guix gc to clear them out or will that delete stuff i'm just going
> to need again?
I'm not entirely certain...but you would always build them again...
>
> Cheers,
> Z
>
> (I presume attachments work ok on this list.)
>
>
>
>
--
Joshua Branson
Sent from Emacs and Gnus
next prev parent reply other threads:[~2019-12-13 14:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 22:31 jfs, jfsutils? Michael Zucchi
2019-12-11 22:38 ` Josh
2019-12-11 23:49 ` Michael Zucchi
2019-12-11 23:57 ` Tobias Geerinckx-Rice
2019-12-12 1:41 ` Tobias Geerinckx-Rice
2019-12-12 3:18 ` Michael Zucchi
2019-12-13 14:31 ` Joshua Branson [this message]
2019-12-13 16:07 ` Tobias Geerinckx-Rice
2019-12-13 16:23 ` Tobias Geerinckx-Rice
2019-12-14 1:15 ` Michael Zucchi
2019-12-30 23:38 ` Michael Zucchi
2019-12-31 0:42 ` Josh Marshall
2019-12-31 6:26 ` Michael Zucchi
2020-01-05 19:04 ` Gábor Boskovits
2020-01-06 7:20 ` Michael Zucchi
2019-12-13 14:33 ` Packing bcachefs " Joshua Branson
2019-12-13 15:32 ` Packaging bcachefs Tobias Geerinckx-Rice
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=86mubwi9eu.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@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.
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).