From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist initial impressions
Date: Thu, 18 May 2023 11:28:07 +0200 [thread overview]
Message-ID: <ZGXvp2/fYhgVQmwt@lenoch> (raw)
In-Reply-To: <ZGT8s6Ixg7r60gNW@titan>
Hi,
On Thu, May 18, 2023 at 02:11:31AM +1000, Jookia wrote:
> Hello ptxdist friends,
[snip]
> Compared to buildroot's 'download and run make menuconfig' ptxdist has a
> pretty hard hill to climb, especially with having to download toolchains
> and BSPs and dealing with some of the package bugs.
>From all the previous lenghty explanation I didn't get what you did
wrong, so I cannot provide any advice. I normally just download and
run build inside BSP :)
> I don't quite understand what's gained by having an installable ptxdist
> and a DistroKit BSP if you're just going to modify both when building
> your system. Maybe someone could explain this to me?
Well, you do not need to modify PTXdist itself, unless there is a bug
somewhere...
But having to install it (or any such build tool in general) is
something Rob Landley whined about two decades ago and it is one of
those rare opinions I agree with him. However I'm unable to find
his post anymore, so I cannot properly quote him.
PTXdist already checks if it is build at each run, so actually builing
it is not that hard. I remember we discussed it few times on the IRC,
but there was never a conclusion. Parhaps we can discuss it now?
ladis
next prev parent reply other threads:[~2023-05-18 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 16:11 Jookia
2023-05-18 9:28 ` Ladislav Michl [this message]
2023-05-18 12:23 ` Jookia
2023-05-18 18:51 ` Ladislav Michl
2023-05-24 10:34 ` Alexander Dahl
2023-05-24 11:28 ` Ladislav Michl
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=ZGXvp2/fYhgVQmwt@lenoch \
--to=oss-lists@triops.cz \
--cc=ptxdist@pengutronix.de \
/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