[josm-dev] livegps plugin update for new gpsd 2.9x (future 3.0) protocol

[Bodo Meissner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 09.06.2010 10:08, schrieb Dirk Stöcker:
> On Wed, 9 Jun 2010, Gleb Smirnoff wrote:
> 
>> I am used to a practice when foreign source is maintained in $REPO/vendor,
>> where new releases of foreign source are imported. And this code doesn't
>> participate in build. Then it is 'svn merge'd to $REPO/smth/smth/foo and
>> optionally modified, if needed, and then used in build. Looks like there is
>> no such practice in OSM. Can we introduce it? Would be there a benefit
>> comparing to committing .jar?
> 
> Currently OSM repo seems to use the ".jar" in "lib" approach. I don't 
> think introducing a new method would be helpful.

I think it is a good idea to save the matching source code in addition to the .jar file. It might pose problems later if at some time the source code will disappear from its original location. (It would even violate licenses like (L)GPL if the corresponding source is not available.)
If the jar has to be built from source this should be done whenever a new version is imported, if a pre-built jar is used it should always be downloaded together with the corresponding source version.


Bodo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkwPU4gACgkQnMz9fgzDSqd24wCfXhBw4PEfr/jU6KBTrXsudmTn
aUEAnRF9q6XeLOvwoOoNos5AuMo0+rr9
=0/CC
-----END PGP SIGNATURE-----