Re: Updating Eclipse

2015-01-14 Thread Thorsten Glaser
On Wed, 14 Jan 2015, Paul Wise wrote: > > Really? Without internet access? > > When we say without Internet access, we mean with access to the Debian > archive (via Build-Depends) but not access to random websites on the And the list of Build-Depends is static. At the time the actual package

Re: Updating Eclipse

2015-01-14 Thread Markus Koschany
I think Paul and Emmanuel have answered the general questions already, so I'd just like to comment on these questions. On 13.01.2015 21:09, Pascal Rapicault wrote: > What drives the decision to package certain Eclipse libraries as system > jars and not others (e.g. swt and osgi, but not emf or jfa

Re: Updating Eclipse

2015-01-14 Thread Emmanuel Bourg
Le 13/01/2015 21:09, Pascal Rapicault a écrit : > - What drives the decision to package certain Eclipse libraries as > system jars and not others (e.g. swt and osgi, but not emf or jface > whereas they can run on plain java as well)? We have a Java Policy [1] that requires jars to be installed in

Re: Updating Eclipse

2015-01-14 Thread Emmanuel Bourg
Le 14/01/2015 02:41, Paul Wise a écrit : >> Yes, this is true especially in the Maven world since it guarantees >> build reproducibility. > > We plan to solve that in Debian by recording versions of > build-dependencies at build time and reproducing the build environment > when doing build re