I can see what you are saying and thus agree that it would be beneficial for the build system in general to always generate the release style artifacts. However I don't see that this means we shouldn't use what we have at our disposal now in order to give our users a better experience than we currently are.
Robbie > -----Original Message----- > From: Rafael Schloming [mailto:rafa...@redhat.com] > Sent: 09 December 2009 17:45 > To: dev@qpid.apache.org > Subject: Re: Release artifacts > > Robbie Gemmell wrote: > > I'm not meaning to suggest doing any complex transformations, rather > using what is already there. We have single-component packages that we > already release separately for all these items, I'm just talking about > whacking the relevant ones in a new tar and calling job done, instead > of having a mashup that contains things people don't want or that can't > even be used together. > > My issue with this is that the single-component packages weren't done > according to the "philosophy" of the build system, and as such the > process for producing component release artifacts diverges somewhat > significantly from the process for producing build artifacts. So while > what you suggest might not involve additional complex transformations, > it does result in something that I would prefer to avoid, which is two > separate systems, one for producing build artifacts, and the other for > producing release artifacts. > > --Rafael > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
