[Bug default/22971] RFE: Support <xi:include> for managing abixml documents.

[dodji at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=22971

--- Comment #1 from dodji at redhat dot com ---
"carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> writes:

> Can we get this feature into libabigail?

Sure.  And very interesting feature.


Though, please keep in mind that initially, the abixml file was not
meant to be edited (or consumed) by humans.  Its format is meant as a
private implementation detail of Libabigail.  Things that interact with
the abixml file are tools.

But then things change, don't they :-)

With that said, I would like to learn more about how you see the whole
process, i.e, how you'd like to split the abixml file to begin with.

I think doing it by hand can be a nightmare as each abixml file has a
number of invariants to comply with.

The way I see things is that we'd need to be able designate (in a high
level-ish manner) which ABI artifact 'A' -- be it a type, function, or
elf symbol -- should be put inside an ancillary abixml file 'AF'.  The
tool would then make sure that the artifacts that 'A' depends on will
also be moved to that 'AF' abixml file.  Things like that.

The main abixml file 'MF' would then include 'AF'.  We could even go
further and saying that using xi:include for that or not is, again, an
implementation detail, even if I think that xi:include seems to be the
way to go :-)


> For example in the relationship between glibc and Fedora glibc, one being the
> downstream of the other, in Fedora I would like move any ABI changes into a
> distinct file and <xi:include> it into the baseline glibc abixml file.

I am not sure I understand the use case correctly.

I would thought that it's the Fedora ABI would have Fedora-specific ABI
sub-parts.  And so the main Fedora ABI description file would include
the "generic" upstream glibc common ABI and define its specific ABI
sub-parts on top of that.

I guess I am understanding something backward.  What is it?

-- 
You are receiving this mail because:
You are on the CC list for the bug.