From: Nathan Dehnel <ncdehnel@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: gnu-build-system not handling pkg-config properly in package definition
Date: Sat, 26 Dec 2020 23:27:38 -0600 [thread overview]
Message-ID: <CAEEhgEtbvRMjybyW7Q0-OgT3y-rx3BLPSO4y8ym2W2KqCj_csw@mail.gmail.com> (raw)
In-Reply-To: <87zh239tid.fsf@nckx>
>However, if you need/want a working Guix bcache-tools package
ASAP, I have to admit I've been sitting on the attached patch for
so long I that forgot it wasn't upstream yet.
Thanks, I will try it out.
>Sounds useful. What does this patch do? Is it related to Guix
(perhaps our blkid)?
I don't actually know. It was taken from gentoo. I was trying to see
if it would fix the build error.
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-fs/bcache-tools/files/1.0.8_p20140220
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-fs/bcache-tools/files/1.1
On Thu, Dec 24, 2020 at 8:19 AM Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>
> Nathan,
>
> Nathan Dehnel 写道：
> > (define-public bcache-tools
>
> So... if you want to learn how to write and submit packages to
> Guix -- please do! And don't let me distract you. Your patch
> looks good, if incomplete :-)
>
> However, if you need/want a working Guix bcache-tools package
> ASAP, I have to admit I've been sitting on the attached patch for
> so long I that forgot it wasn't upstream yet.
>
> > (patches (search-patches "bcache-tools-noprobe.patch"))
>
> Sounds useful. What does this patch do? Is it related to Guix
> (perhaps our blkid)?
>
> > (synopsis "These are the userspace tools required for
> > bcache.")
> > (description "Bcache patches for the Linux kernel allow one
> > to use
> >SSDs to cache other block devices. It's analogous to L2Arc for
> >ZFS,
> >but Bcache also does writeback caching (besides just write
> >through
> >caching), and it's filesystem agnostic. ")
>
> I think The GNU Way is ‘user space’, ‘file system’, ‘write-back’
> etc. Be sure to double-space prose sentences; ‘guix lint
> bcache-tools’ will warn you about this and other possible surface
> issues.
>
> This description sounds out of date (it's been upstream since the
> 3.x days) and the ZFS comparison is presumably meaningful only to
> a small minority of ZSF-on-Linux-Libre users. IMO try to describe
> packages in first-class terms so users don't get sent on a rabbit
> chase.
>
> Feel free to snarf my description but don't feel obligated either.
>
> Kind regards,
>
> T G-R
>
prev parent reply other threads:[~2020-12-27 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 5:33 gnu-build-system not handling pkg-config properly in package definition Nathan Dehnel
2020-12-24 12:59 ` Danny Milosavljevic
2020-12-24 14:19 ` Tobias Geerinckx-Rice
2020-12-24 15:30 ` Tobias Geerinckx-Rice
2020-12-27 5:27 ` Nathan Dehnel [this message]
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=CAEEhgEtbvRMjybyW7Q0-OgT3y-rx3BLPSO4y8ym2W2KqCj_csw@mail.gmail.com \
--to=ncdehnel@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).