From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marko Lindqvist <cazfi74@gmail.com>
Cc: Randolph Sapp <rs@ti.com>,
alex.kanavin@gmail.com,
openembedded-core@lists.openembedded.org,
Ryan Eatmon <reatmon@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
cordlandwehr@kde.org,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Subject: Re: [oe-core] [RFC] meson.bbclass: pkg-config vs pkgconf
Date: Mon, 03 Jun 2024 22:37:56 +0100 [thread overview]
Message-ID: <43bdffe76547583062c308a8dc2474eb4365d474.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAF6bG8ePV1ti4E91k9=0RFZ5_i=OCHStde0few-qR+MKadQWvQ@mail.gmail.com>
On Tue, 2024-06-04 at 00:32 +0300, Marko Lindqvist wrote:
> On Tue, 4 Jun 2024 at 00:22, Richard Purdie via
> lists.openembedded.org
> <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
> >
> > Keeping it simple and saying "pkg-config behaviour"
> > everywhere is simpler IMO.
>
> Do you think that pkg-config will still gain livelihood? I've
> considered it a dead project for some time now. I was about to check
> how many years it's since the latest commit to their repository, but
> the repo URL from freedesktop site now gave 404.
It hasn't really needed to change to be honest. I do agree the 404 is
worrying and it has been a long time since there was a release.
The trouble is, who wants to take on chasing down all the bugs and
pushing changes to all the upstreams that will need patching? In
general people fix a small corner of the problem then get
bored/frustrated/distracted/whatever and move on to something else, not
that I blame them. This isn't a conversion we can half do, it will end
up as another flag day :/.
Cheers,
Richard
next prev parent reply other threads:[~2024-06-03 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 18:02 [oe-core] [RFC] meson.bbclass: pkg-config vs pkgconf Randolph Sapp
2024-06-03 21:22 ` Richard Purdie
2024-06-03 21:32 ` Marko Lindqvist
2024-06-03 21:37 ` Richard Purdie [this message]
2024-06-03 21:54 ` Randolph Sapp
2024-06-03 22:02 ` Randolph Sapp
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=43bdffe76547583062c308a8dc2474eb4365d474.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=cazfi74@gmail.com \
--cc=cordlandwehr@kde.org \
--cc=denys@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=reatmon@ti.com \
--cc=rs@ti.com \
/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