From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: AW: AW: [PATCH] First Patch from me. Hope this Ok so. Socat, filan and procan.
Date: Thu, 05 Nov 2020 07:38:33 +0100 [thread overview]
Message-ID: <aa76d5bd-5da9-616c-f8de-6e42c4e6a243@ipfire.org> (raw)
In-Reply-To: <000001d6b2f6$6ae8a9e0$40b9fda0$@v16.de>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
On 04.11.2020 23:04, smooky(a)v16.de wrote:
> Hi Matthias.
Hi,
> Does that mean I should have included the customized make.sh with the patch?
Exactly. ;-)
> I didn't do that with lshw and ncdu either, but everything seems to work.
Both exist in 'make.sh' - no need to add. They were both added by MT
(2020-09-21).
=>
https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=make.sh;h=9ddfd4c07bcf6f1f0ec01097b971afa5d8bd7a02;hb=refs/heads/master#l1649
Added by MT:
=>
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;f=make.sh;h=4d275bcd1f86383a82625a674ef05bc8738d889b
...and:
=>
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;f=make.sh;h=76c5f3e0d96525c419faa3e69d7592d3e3d0965b
If you add a *new* package to the distribution, an appropriate lfsmake2
... -line must be added to 'make.sh' or nothing will be compiled.
Best,
Matthas
> best regards
>
> Marcel Follert
>
> -----Ursprüngliche Nachricht-----
> Von: Matthias Fischer <matthias.fischer(a)ipfire.org>
> Gesendet: Mittwoch, 4. November 2020 22:17
> An: smooky(a)v16.de; development(a)lists.ipfire.org
> Betreff: Re: AW: [PATCH] First Patch from me. Hope this Ok so. Socat, filan and procan.
>
> Hi,
>
> something like
>
> ...
> lfsmake2 socat
> ...
>
> is missing in 'make.sh'.
>
> 'socat' wasn't built.
>
> HTH,
> Matthias
>
> On 04.11.2020 21:35, smooky(a)v16.de wrote:
>> Hey all.
>>
>> Does anyone happen to have an idea why the socat package offered by
>> Pakfire does not contain any program data?
>> It only contains the install.sh, uninstall.sh, update.sh, ROOTFILES
>> and an empty .tar.xz archive.
>> Seen here
>> https://mirror1.ipfire.org/pakfire2/2.25-x86_64/paks/socat-1.7.3.4-1.ipfire.
>> The .tar.xz archive is filled with my locally created version.
>>
>> best regards
>>
>> Marcel Follert
>>
>>
>
>
>
next prev parent reply other threads:[~2020-11-05 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200729212025.28443-1-user@router.home.v16.de>
2020-11-04 20:35 ` smooky
2020-11-04 21:16 ` Matthias Fischer
2020-11-04 22:04 ` AW: " smooky
2020-11-05 6:38 ` Matthias Fischer [this message]
2020-11-04 21:19 ` Matthias Fischer
2020-11-06 10:24 ` Michael Tremer
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=aa76d5bd-5da9-616c-f8de-6e42c4e6a243@ipfire.org \
--to=matthias.fischer@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