Re: [oscar-devel] Packaging Bundles

[Richard S. H. <he...@un...>]

Nektarios K. Papadopoulos wrote:

> We are talking about source-bundle and indeed the download/compile 
> phase is, in most cases, going to happen on a host with high speed 
> internet access and gigabytes of hard drive. But the situation for 
> embedded devices is different. Both download time and storage space 
> have to be considered.


While I agree with your point, your initial comment is more important. I 
don't expect that people will be downloading the source code to a PDA or 
cell phone, so the source packaging structure is not for that purpose.

The whole point is this: bundle source code will no longer be included 
with Oscar, each bundle will be treated as a separate subproject at 
Oscar's old site and I wanted some simple way for people to be able to 
get the source code.

In truth, we don't need OBR to provide access to the source at all, but 
since the source for each bundle will need to be URL accessible anyway, 
I thought it would be nice to include that meta-data in OBR with a 
simple command to download it.

> A feature I would like to see in those source-bundles is a build 
> option like say 'ant strip' that produce multitpl bundles. The main 
> bundle and one bundle for each required library.


An interesting idea, but I am not sure it is a good one, because this 
means that the bundle may end up getting versions that it didn't expect 
and in the case of libraries, this is not a good thing, since they are 
not always backwards compatible.

-> richard