Re: [cp-patches] FYI: X peers
> "Roman" == Roman Kennke <[EMAIL PROTECTED]> writes: Roman> Mark proposed to put jars that are (optionally) needed for classpath on Roman> http://builder.classpath.org/ somewhere. What do others think? This seems like a reasonable idea to me. Tom
Re: [cp-patches] FYI: X peers
On Sat, Jul 01, 2006 at 08:22:46PM +1000, Raif S. Naffah wrote: > hello Michael, > > On Saturday 01 July 2006 20:05, Michael Koch wrote: > > On Sat, Jul 01, 2006 at 10:33:10AM +0200, Roman Kennke wrote: > > > Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah: > > > > On Friday 30 June 2006 01:27, Roman Kennke wrote: > > > > > I checked in the Escher-based X peers and added some configury > > > > > for enabling it. To build the X peers you need the most recent > > > > > Escher library, to be found here: > > > > > > > > > > http://kennke.org/~roman/escher-0.3.0.jar > > > > > > > > > > Configure with: --with-escher=/path/to/escher-0.3.0.jar > > > > > --enable-local-sockets > > > > > > > > would it make sense to create a new folder, say "external-jars" > > > > and include the latest escher (and other java-only external > > > > dependencies) jar(s) there. --with-escher can use that > > > > jar/location by default, otherwise the full path to a > > > > distro's/user's location of that jar can be fed to configure. > > > > > > This makes sense. I am all for it. > > > > > > Mark proposed to put jars that are (optionally) needed for > > > classpath on http://builder.classpath.org/ somewhere. What do > > > others think? > > > > Don't put jars without sources into classpath releases. Otherwise > > Distros will need to alter the upstream tarball and remove this. And > > altering removes the feature that people can easily check if the > > upstream sources used by a distro is really what upstream released. > > would including the jar of the sources --e.g. escher-0.3.0.jar and > escher-0.3.0-src.jar-- address that concern. Not for Debian as this makes it impossible to patch security issues easily. Cheers, Michael -- http://www.worldforge.org/
Re: [cp-patches] FYI: X peers
hello Michael, On Saturday 01 July 2006 20:05, Michael Koch wrote: > On Sat, Jul 01, 2006 at 10:33:10AM +0200, Roman Kennke wrote: > > Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah: > > > On Friday 30 June 2006 01:27, Roman Kennke wrote: > > > > I checked in the Escher-based X peers and added some configury > > > > for enabling it. To build the X peers you need the most recent > > > > Escher library, to be found here: > > > > > > > > http://kennke.org/~roman/escher-0.3.0.jar > > > > > > > > Configure with: --with-escher=/path/to/escher-0.3.0.jar > > > > --enable-local-sockets > > > > > > would it make sense to create a new folder, say "external-jars" > > > and include the latest escher (and other java-only external > > > dependencies) jar(s) there. --with-escher can use that > > > jar/location by default, otherwise the full path to a > > > distro's/user's location of that jar can be fed to configure. > > > > This makes sense. I am all for it. > > > > Mark proposed to put jars that are (optionally) needed for > > classpath on http://builder.classpath.org/ somewhere. What do > > others think? > > Don't put jars without sources into classpath releases. Otherwise > Distros will need to alter the upstream tarball and remove this. And > altering removes the feature that people can easily check if the > upstream sources used by a distro is really what upstream released. would including the jar of the sources --e.g. escher-0.3.0.jar and escher-0.3.0-src.jar-- address that concern. cheers; rsn pgpMCTxdlwulF.pgp Description: PGP signature
Re: [cp-patches] FYI: X peers
On Sat, Jul 01, 2006 at 10:33:10AM +0200, Roman Kennke wrote: > Hi Raif, > > Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah: > > hello Roman, > > > > On Friday 30 June 2006 01:27, Roman Kennke wrote: > > > I checked in the Escher-based X peers and added some configury for > > > enabling it. To build the X peers you need the most recent Escher > > > library, to be found here: > > > > > > http://kennke.org/~roman/escher-0.3.0.jar > > > > > > Configure with: --with-escher=/path/to/escher-0.3.0.jar > > > --enable-local-sockets > > > > would it make sense to create a new folder, say "external-jars" and > > include the latest escher (and other java-only external dependencies) > > jar(s) there. --with-escher can use that jar/location by default, > > otherwise the full path to a distro's/user's location of that jar can > > be fed to configure. > > This makes sense. I am all for it. > > Mark proposed to put jars that are (optionally) needed for classpath on > http://builder.classpath.org/ somewhere. What do others think? Don't put jars without sources into classpath releases. Otherwise Distros will need to alter the upstream tarball and remove this. And altering removes the feature that people can easily check if the upstream sources used by a distro is really what upstream released. Michael -- http://www.worldforge.org/
Re: [cp-patches] FYI: X peers
Hi Raif, Am Samstag, den 01.07.2006, 09:24 +1000 schrieb Raif S. Naffah: > hello Roman, > > On Friday 30 June 2006 01:27, Roman Kennke wrote: > > I checked in the Escher-based X peers and added some configury for > > enabling it. To build the X peers you need the most recent Escher > > library, to be found here: > > > > http://kennke.org/~roman/escher-0.3.0.jar > > > > Configure with: --with-escher=/path/to/escher-0.3.0.jar > > --enable-local-sockets > > would it make sense to create a new folder, say "external-jars" and > include the latest escher (and other java-only external dependencies) > jar(s) there. --with-escher can use that jar/location by default, > otherwise the full path to a distro's/user's location of that jar can > be fed to configure. This makes sense. I am all for it. Mark proposed to put jars that are (optionally) needed for classpath on http://builder.classpath.org/ somewhere. What do others think? /Roman -- “Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.” - William Blake signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
