Improving source drops documentation
Dr Andrew John Hughes
ahughes at redhat.com
Wed Oct 12 07:50:44 PDT 2011
On 13:52 Wed 12 Oct , Fredrik Öhrström wrote:
> 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.
Yes, same in the IcedTea forest e.g. http://hg.openjdk.java.net/icedtea/jdk7/jaxws/rev/c608b38af726
> > 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
> immediately needed.
I still fail to see why such changes would be approved in the first place. It sounds like a software
solution is being used to paper over a social one.
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and IcedTea
PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
More information about the build-dev