Closed AMDmi3 closed 2 years ago
Some patches, like in Gentoo, is distro specific and need to correct build of package.
Yes, same with FreeBSD. I can't think of a way to sort this out automatically, but this still is a useful info. A bit heavy to retrieve though.
There is a sentence simply to specify existence of patches for a packet. And there can be as we will invent … (=
What I've meant is that while the information on patches is easily retrievable for e.g. Gentoo (as we already have the whole repository and all we need is to look into files/
for each package), for other repos it's not that trivial - for instance, we only retrieve single INDEX file for FreeBSD now, but in order to discover patches we'll have to get whole ports repository and parse it as well. Even more complex for other repos. It may be done gradually though.
we need is to look into files/ for each package
We also need to look into Manifest
file and in .ebuild
.
In Manifest
listed ALL files for package. In .ebuild
patches maybe listed in ${PATCHES}
, *`${EPATCH_}** and **
${SRC_URI}`** variables and still somewhere.
We also need to look into Manifest file
Why? It just lists checksums.
and in .ebuild
Yes, but it looks to be more complex. For example, app-emacs/teco, uses ${ELISP_PATCHES}
, in which it references other variable.
Emacs, this separate, it is written on Lisp therefore plugins to it so collect, mostly.
This that still a some magic to rake .eclasses
from /path/to/portage/tree/eclasses
folder which use .ebuilds
from «inherit … keyword».
This is supported by package-specific links
Some repos include patches, it would be nice to report them upstream.