From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ./xbps-src bootstrap fixes
Date: Wed, 22 Apr 2020 00:49:13 +0200 [thread overview]
Message-ID: <20200421224913.ZRq_mG2KkKOhPXt18KW0bGorPkMAFlkDo-Cr-rx3TuI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21226@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617452566
Comment:
Hm, ok. It seems I misunderstood the way the bootstrap is meant to work. I like that it should be as minimalistic as possible.
Let me just clarify; the right way forward with m4 is to remove the need for texinfo when `./xbps-src bootstrap` is run? (ie, remove the doc generation?)
What is the correct way to then make m4 use texinfo inside the chroot? Would it be the creation of a `chroot-m4` package?
@xtraeme You say bootstrap vs chroot case in your review comments - how do you distinguish between the two?
Sorry for the questions, I think I'm missing something.
next prev parent reply other threads:[~2020-04-21 22:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 22:14 [PR PATCH] " fosslinux
2020-04-21 22:16 ` xtraeme
2020-04-21 22:18 ` xtraeme
2020-04-21 22:35 ` pullmoll
2020-04-21 22:35 ` pullmoll
2020-04-21 22:38 ` xtraeme
2020-04-21 22:49 ` fosslinux [this message]
2020-04-21 22:52 ` pullmoll
2020-04-21 22:54 ` fosslinux
2020-04-21 22:59 ` xtraeme
2020-04-21 23:08 ` pullmoll
2020-04-21 23:10 ` xtraeme
2020-04-21 23:16 ` fosslinux
2020-04-21 23:17 ` pullmoll
2020-04-21 23:19 ` xtraeme
2020-04-21 23:21 ` xtraeme
2020-04-21 23:22 ` pullmoll
2020-04-21 23:23 ` xtraeme
2020-04-21 23:24 ` xtraeme
2020-04-21 23:26 ` pullmoll
2020-04-21 23:28 ` xtraeme
2020-04-21 23:31 ` xtraeme
2020-04-21 23:35 ` pullmoll
2020-04-21 23:36 ` pullmoll
2020-04-21 23:47 ` pullmoll
2020-04-22 0:33 ` fosslinux
2020-04-22 0:36 ` [PR PATCH] [Closed]: " pullmoll
2020-04-22 0:36 ` pullmoll
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=20200421224913.ZRq_mG2KkKOhPXt18KW0bGorPkMAFlkDo-Cr-rx3TuI@z \
--to=fosslinux@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).