From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Michael Zucchi <notzed@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: jfs, jfsutils?
Date: Fri, 13 Dec 2019 17:07:48 +0100 [thread overview]
Message-ID: <87lfrgi4yz.fsf@nckx> (raw)
In-Reply-To: <4454c84b-fa97-df27-d5d5-7e7a8643f8ef@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2875 bytes --]
Michael,
Michael Zucchi 写道:
> 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.
That's great! Shame about the duplicated effort, but such things
happen.
> I'm not really sure where to put it or how to compile each part
> (it just
file-systems.scm if possible. linux.scm is already a bloated
grab-bag.
For now, you can test each package at a time by adding the
variable (e.g ‘jfs_fsck/static’) as the last line of your current
.scm file. This will make the file ‘evaluate to jfs_fsck/static’,
so you can:
$ guix build -f thefile.scm
You'll have to change that last line every time you want to change
the package being built.
You'll need a Guix git checkout to get much further. If you
haven't yet done so, read ‘Building from Git’ in the manual and
bootstrap yourself some Guix.
Then you can copy your 3 package expressions to file-systems.scm,
keeping it in alphabetical order or at least not making things
worse. After making some small adjustments like adding a license:
prefix, you can build your packages with:
~/guix$ ./pre-inst-env guix build jfsutils
> build jfsutils, not jfs_fsck/static) and I used the slackware
> patches,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Typo that should be the other way 'round?
Are you sure that LDFLAGS=-static is needed when using
static-package? Here's my aborted static version:
++(define-public jfsutils/static
++ (static-package
++ (package
++ (inherit jfsutils)
++ (name "jfsutils-static")
++ (inputs
++ `(("util-linux" ,util-linux)
++ ("util-linux:static" ,util-linux "static"))))))
I got my patches from Debian, but they do the same job. There
were others[0] but they weren't vital or relevant to Guix.
> 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?
It will by default remove the ‘build’ dependencies, yes.
I advise against GC'ing unless you desperately need space, and it
won't come from a handful of relatively tiny stale JFSutils. Guix
also deduplicates the store by default. At file level, even.
> (I presume attachments work ok on this list.)
Sure.
;; COPYING is gpl3, the headers are gpl2+?
That's interesting. Where'd you find gpl2+?
Kind regards,
T G-R
[0]: https://sources.debian.org/patches/jfsutils/1.1.15-4/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-12-13 16:07 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
2019-12-13 16:07 ` Tobias Geerinckx-Rice [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfrgi4yz.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=notzed@gmail.com \
/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.