Re: Plasma build order issue: oxygen and oxygen-sounds

On Thu, 2024-10-31 at 22:01 -0600, jeremy wiig wrote:
> On Thu, Oct 31, 2024 at 9:50 PM Bruce Dubbs
> <[email protected]> wrote:
> > 
> > On 10/31/24 22:26, Xi Ruoyao ([email protected] via blfs-dev Mailing List) wrote:
> > > On Thu, 2024-10-31 at 21:04 -0600, jeremy wiig wrote:
> > > > Building plasma with jhalfs results in oxygen not generating a build
> > > > script. This is due to the following processing in make_book.xsl:
> > > > 
> > > > <!-- $package must start with a space, and finish with a "-", to be
> > > >           sure to match exactly the package. Note that if we have two
> > > >           packages named e.g. "pkg1" and "pkg1-add", the second one may be
> > > >           matched by " pkg1-". So this only works if "pkg1" comes before
> > > >           "pkg1-add" in the md5 file. Presently this is the case in the book...
> > > >      -->
> > > > 
> > > > and oxygen-sounds comes before oxygen in the plasma build list. Moving
> > > > oxygen-sounds to the end of the list after oxygen fixes the issue.
> > > 
> > > The problem here is jhalfs BLFS support is just bit-rotting when Pierre
> > > is AFK.  We really need a new maintainer if we want to keep jhalfs BLFS
> > > support.
> > 
> > I agree with Xi.  I believe the BLFS side of ALFS is not of great use for developers
> > who do one package at a time and modify book pages virtually daily. IMO the BLFS
> > section of ALFS is targeted more towards users who just want to build a fresh system.
> > 
> > The current book maintainers really don't have the time to do updates to jhalfs.
> > 
> >    -- Bruce
> > 
> > --
> > http://lists.linuxfromscratch.org/sympa/info/blfs-dev
> > Unsubscribe: See the above information page
> 
> would you then suggest i create my own jhalfs repository then?
> continue to share patches to the alfs mailing list in the hopes that
> someone will commit them? will you be willing to make trivial changes
> to the book to accommodate, such as reordering the md5 list for
> plasma?

Yes that'll be a good start.  And maybe we'll start to run a GitLab
instance on linuxfromscratch.org to make contributing easier (but the
work has just begun and we are still experimenting).

But a problem: is there any editor monitoring alfs list as at now?

In the meantime should we move/mirror jhalfs to GitHub or somewhere to
allow easier contribution as we don't have too much time on it?

> i have no issue with and am perfectly capable of troubleshooting and
> fixing the software as long as i'm using it, much like yourselves.

Thanks!

-- 
Xi Ruoyao <[email protected]>
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page