From: Efraim Flashner <efraim@flashner.co.il>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33896@debbugs.gnu.org
Subject: bug#33896: libblockdev inputs are not used correctly
Date: Sat, 29 Dec 2018 20:50:36 +0200 [thread overview]
Message-ID: <20181229185036.GV2581@macbook41> (raw)
In-Reply-To: <20181228143255.78bf15b1@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Fri, Dec 28, 2018 at 02:32:55PM +0100, Danny Milosavljevic wrote:
> Currently, libblockdev has inputs which aren't used.
>
> These SHOULD be used, but the source files are not patched
> so the executables in the inputs are not found or used.
>
> Example:
>
> * libblockdev depends on dosfstools because src/plugins/fs/vfat.c would use
> "mkfs.vfat" etc, but src/plugins/fs/vfat.c is not patched to actually refer
> to the inputs.
>
> This problem is valid for everything in src/plugins/fs .
>
> Do we proceed to patch it to use the inputs or do we move dosfstools etc
> to propagated-inputs ?
>
> I'd suggest the former.
Similar to the enlightenment package getting more 'substitute*'s to
improve functionality, I agree that patching libblockdev to actually
find all the inputs/executables is preferable.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-29 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 13:32 bug#33896: libblockdev inputs are not used correctly Danny Milosavljevic
2018-12-29 18:50 ` Efraim Flashner [this message]
2019-01-05 17:55 ` Ludovic Courtès
2021-09-25 21:28 ` bug#33896: [PATCH 1/2] gnu: libblockdev: Embed executable paths Sarah Morgensen
2021-09-25 21:46 ` bug#33896: [PATCH 2/2] gnu: libblockdev: Fix inputs Sarah Morgensen
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=20181229185036.GV2581@macbook41 \
--to=efraim@flashner.co.il \
--cc=33896@debbugs.gnu.org \
--cc=dannym@scratchpost.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.
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.