On Thu, 08 Jun 2023 14:46:01 +0300
Wael Karram <[email protected]> wrote:
> As far as I see it, it is preferable to replace flashrom with
> flashrom-stable, and not because of just rust (although that would
> mean being simpler and lighter to build).
I've looked at the release notes of flashrom 1.3 and I've also
installed flashrom-stable and flashrom-stable is at least missing the
following features:
- I2C support
- Write protection support

So for these reasons it might be great to have both. Though it would
require someone to package flashrom 1.3.

Also I don't think we need to necessarily convince upstream to switch to
flashrom-stable but we could probably tell them that it exists and that
it's easier to package and have them make their choice. 

If they manage to package flashrom 1.3 we'd then get both.

Also both flashrom and flashrom-stable seem to be developed under the
same project and infrastructure (releases are on the same server), so
it doesn't look like the usual forks of projects from Coreboot (like
with memtest86+ and similar projects). 

It might be interesting to have more information about the relationship
between both projects (I didn't find any official text describing that)
for the package description. I've tried to look rapidly but I didn't
find any infos.

For instance there is a Flashrom-stable/1.1 page on flashrom wiki but
even on Flashrom-stable/1.0 which seems to be the first release ("The
1.0 release comprise about 300 patches [...] on top of flashrom v1.2.1")
there is no information about that. 

The source code of the 1.0 and 1.1 releases also don't seem to have any
mention of flashrom-stable beside for the bugreport address and the git
URL, and for when printing the flashrom version. 

So if you came across that information somewhere it might be
interesting. If you didn't, then we could try to explain why
flashrom-stable is relevant ourselves in the pkgdesc. 

The Flashrom-stable/1.0 wiki page has the following: "We skipped
invasive patches so hopefully it will still build on all platforms
where flashrom v1.2 built".

- pkgdesc="Flashrom is a utility which can be used to detect, read,
  erase, or write BIOS chips (DIP, PLCC, SPI)."
+ pkgdesc="Flashrom is a utility which can be used to detect, read,
  erase, or write BIOS chips (DIP, PLCC, SPI). This
  flashrom-stalbe version doesn't require rust, so it is easier to
  build and it still builds fine on the same platforms supported by
  flashrom v1.2"

Also DIP and PLCC are chip packages / formats, so it could probably be
improved to "FWH, LPC, Parallel, SPI" which are the protocols
supported. This mistake seems to come from the flashrom-git aur package
that was probably used as a base for the flashrom-stable aur package.

As for the chip package / formats, flashrom doesn't have to care about
them as it's more a hardware thing, so we can omit them completely.

It's a bit like if a laptop has a strange USB 2.0 connector, the
software would not be able to see the difference.

Denis.

Attachment: pgpr5pLQnwIXh.pgp
Description: OpenPGP digital signature

_______________________________________________
Dev mailing list
[email protected]
https://lists.parabola.nu/mailman/listinfo/dev

Reply via email to