Improving source drops documentation
oehrstroem at gmail.com
Wed Oct 12 04:52:28 PDT 2011
2011/10/12 Dr Andrew John Hughes <ahughes at redhat.com>:
> FWIW, I recently did exactly that in IcedTea because I'm sick of all the problems this drop solution causes.
> This has cut things down from needing five tarballs (jaxp + jaxws repositories + three drop zips) to two with
> everything in. Should someone really want to build from the tarballs, they can just delete the sources.
The sources must be added to the jaxp/jaxws repositores. In fact I
have done that already in the build-infra forest.
> I don't see why touching the files is a problem; surely all changesets have to pass review and any that attempt to
> alter this files would just not do so? What am I missing?
It suppose it is a matter of educating sustaining engineering that
fixes to jaxp and jaxws has to go through the upstream repositories.
A bit of software to prevent messing this up would help, but is not
More information about the build-dev