Re: An End User's POV [was libqtxdg-4.2.0 build fails]

"Jean-Marc Pigeon" ([email protected] via blfs-support Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.support
Organization SAFE Inc.
Message-ID <[email protected]>
On Sat, 2025-08-16 at 18:54 +0800, Xi Ruoyao wrote:
> On Sat, 2025-08-16 at 11:29 +0200, Rainer Fiebig wrote:
> > If what Joe Locash said is correct, then any of the three
> > run-time-dependencies for libnotify would suffice.
> 
> To be precise, not "any" but the one corresponding to your desktop
> environment.  We can take the runtime dependency list of polkit as an
> example.
> 
> > I've already made a suggestion that would make that clearer.
> > And perhaps this should even
> > be amended by a note that the two desktop-environment-associated
> > packages would have to be built in the build-order required for
> > that
> > desktop-environment.
> 
> I still think we should track the dependency correctly instead of
> just
> relying on a specific build order.  I often build GNOME in an order
> different from the book.

100% Agreed!!, not only for GNOME but also for many other components...
Problem: far too many linux parts have a loop within
the building order (A -> need B -> need C -> need A).
this because most of the upstream contributor see only their parts
without knowing/keeping/designing applications/parts/libs
withing its specific layer.
This means as "distribution" builder we need to do
compromise/choise and such, result is not predictable/reliable.
(such saying otherwise, "Houston we have problem"); 

Linux from scratch project contribution to linux eco-system
could/should be to encourage upstream contributor to keep
their parts within their designed/known layer.

Ok, this is easier to say than to do, but still...

-- 
a bientôt

Jean-Marc Pigeon
SAFE Inc.

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-support
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.