From: smooky@v16.de
To: development@lists.ipfire.org
Subject: AW: AW: [PATCH] First Patch from me. Hope this Ok so. Socat, filan and procan.
Date: Wed, 04 Nov 2020 23:04:07 +0100 [thread overview]
Message-ID: <000001d6b2f6$6ae8a9e0$40b9fda0$@v16.de> (raw)
In-Reply-To: <d21ff467-9d89-33d2-563c-6c78b34bd8ac@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
Hi Matthias.
Does that mean I should have included the customized make.sh with the patch?
I didn't do that with lshw and ncdu either, but everything seems to work.
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-04 22:04 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 ` smooky [this message]
2020-11-05 6:38 ` AW: " Matthias Fischer
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='000001d6b2f6$6ae8a9e0$40b9fda0$@v16.de' \
--to=smooky@v16.de \
--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