Re: [oscar-devel] Packaging Bundles

[Nektarios K. P. <npa...@in...>]

Richard S. Hall wrote:
> 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.
I agree

> 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.
> 
I understand

> 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.
> 
I realize the implications as well as those pointed out by others. I am 
certainly not in position to describe a bullet-proof versioning - 
dependencies resolving system.
I guess I was 'too' focused in my use scenario, i.e. embedded. So, I'll 
say no more and when I come across two bundles with the same library 
embedded inside them, I'll re-bundlize them myself to save space.

cheers

---
nek