Physical file organisation of any bearing to LGPL?

[Stuart Rossiter]

Hope this question is appropriate for this mailing list (if not, any pointers to 
a better location would be appreciated).

With regards to the LGPL (and other 'library-like' open source licences), is the 
physical organisation of the files distributed ever of any relevance, or only 
the 'logical' links (be they inheritance-related or whatever)?

As a concrete example, say that (in Java) I subclass an LGPL class, and that 
subclass is kept in the same package as its parent (perhaps due to accessing 
protected members, or some run-time dynamic discovery of said classes by the 
LGPL code). So I'd be distributing my code in the same physical directory as the 
LGPL (and, indeed, the same logical package; perhaps this is an additional 
'logical structure' subtlety?).

My assumption is that this makes *no* difference to the usage of the LGPL; it's 
just the same as if my code was in my own distinct package and hence physical 
directory, but wanted to check since this doesn't appear to be covered in the 
(detailed) GNU FAQ entries (or explicitly in the licence itself).

Regards,
Stuart