On 13.10.2015 11:39, hasufell wrote: > On 10/13/2015 09:51 AM, Alexis Ballier wrote: >> >> that would work too, but dtd provides standardization, and avoids >> duplicating package-wide information (meaning of slot/subslot) in every >> single ebuild. >> > > Yeah, the only thing that I wasn't sure about is the subslots part. With > the proposed patch we don't document a subslot for a specific slot, but > for the whole package. Everything else looked too complicated/ugly in > xml and I'm not sure we even need it. If someone has a better idea, > please speak up. > I think it should be kept simple, because we want devs to fill in this > kind of information, not confuse them. >
Should we extend the definition, so it can optionally
include a number of libraries the subslot is created from?
<subslot files>libfoo.so libbar.so libbaz.so</subslot files>
This would enable us to write a tool that checks for changed sonames
automatically (by using some command like find ${DESTDIR} -name
"libsoname.so" and run objdump on it.
Cheers
Manuel
signature.asc
Description: OpenPGP digital signature
