public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] udev: do not generate manpages
Date: Tue, 25 May 2021 20:57:55 +0100	[thread overview]
Message-ID: <8C01F9FD-136E-48D3-82C1-33A48F3F5BDC@ipfire.org> (raw)
In-Reply-To: <ebbaec16-7203-2113-3740-3cbc5b83e999@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

The root file contains man-pages. Disabling them should make them disappear, or what is the point of the whole patch?

> On 25 May 2021, at 20:40, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello Michael,
> 
> thanks for your reply.
> 
> No, as far as I am concerned, this did not induce rootfile changes. Or am I mistaken?
> 
> Thanks, and best regards,
> Peter Müller
> 
>> Hello,
>> 
>> cool. Is the root file update coming in an extra patch?
>> 
>> -Michael
>> 
>>> On 23 May 2021, at 16:46, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>> 
>>> This is probably a typo and was meant to read "--disable-manpages" in
>>> the first place.
>>> 
>>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>>> ---
>>> lfs/udev | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>> 
>>> diff --git a/lfs/udev b/lfs/udev
>>> index b578ab54c..11868ffe2 100644
>>> --- a/lfs/udev
>>> +++ b/lfs/udev
>>> @@ -84,7 +84,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>>> 		--libexecdir=/lib \
>>> 		--with-rootprefix= \
>>> 		--with-rootlibdir=/lib \
>>> -		--enable-manpages \
>>> +		--disable-manpages \
>>> 		--disable-static
>>> 
>>> 	cd $(DIR_APP) && make $(MAKETUNING)
>>> -- 
>>> 2.26.2
>> 


  reply	other threads:[~2021-05-25 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 15:46 Peter Müller
2021-05-23 20:28 ` Adolf Belka
2021-05-25  9:53 ` Michael Tremer
2021-05-25 19:40   ` Peter Müller
2021-05-25 19:57     ` Michael Tremer [this message]
2021-05-25 20:03       ` Peter Müller

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=8C01F9FD-136E-48D3-82C1-33A48F3F5BDC@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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