Opened 5 years ago

Closed 4 years ago

#4489 closed task (overcomebyevents)

bzip2-1.1.0 (Upcoming)

Reported by: Bruce Dubbs Owned by: lfs-book
Priority: normal Milestone: Future
Component: Book Version: SVN
Severity: normal Keywords:
Cc:

Description

From http://lists.linuxfromscratch.org/pipermail/lfs-dev/2019-June/073158.html

There is a new maintainer for bzip2. There is no released tarball yet, but the new repo will be at https://gitlab.com/federicomenaquintero/bzip2

This will complicate LFS quite a bit since it will need meson or cmake. We currently need bzip2 for seven packages (two are ours and can easily be changed) and build it in Chapter 5. When the new package gets released, we will need to analyze the full impact.

One solution we might want to consider is converting the upstream packages that currently use bzip2 to xz or gz and hosting ourselves: elfutils, expat, iana-etc, make, python-docs.

Some packages may offer an alternative compression.

  • The make tarball is available as a gz packages.
  • elfutils only offers bz2.
  • expat offers xz.
  • iana-etc is only bz2, was last updated in 2008, and we already host it on anduin.
  • The python docs also come in a zip format, but that doesn't help. We install python before meson/ninja so there is a circular dependency there.

Change History (4)

comment:1 by Xi Ruoyao, 5 years ago

An annoying problem: if bzip2 is not present, Python bz2 module would be unusable. So the circular dependency is there.

I suggest:

Install a temporary Meson in chapter 5: cp -Rv mesonbuild /tools/lib/python3.7 && install -vm755 meson.py /tools/bin/meson

and, move chapter 5 bzip2 after the temporary meson.

---

But what should we do after bzip2 is "rustified" like hell?

comment:2 by Xi Ruoyao, 5 years ago

Summary: bzip2-1.0.7 (Upcoming)bzip2-1.1.0 (Upcoming)

Bzip2-1.0.7 is still using the Makefile and Makefile-libbz2.so. Meson would be used in Bzip2-1.1.0.

comment:3 by Xi Ruoyao, 5 years ago

Milestone: 8.5Future

comment:4 by Bruce Dubbs, 4 years ago

Resolution: overcomebyevents
Status: newclosed

This does not seem to be moving in the last year. I am removing the ticket. Reopen or create a new ticket when/if upstream releases a new version.

Note: See TracTickets for help on using tickets.