- Nov 18, 2012
-
-
kytv authored
On Debian Squeeze the default-jre-* packages point to gij/gcj which is suboptimal. Openjdk cannot be forced since not all platforms--such as kFreeBSD--have it as an available option.
-
- Jul 23, 2012
-
-
kytv authored
Tomcat6 & Jetty6 are going to be dropped from the next release of Debian stable (Wheezy) in favor of Tomcat7 and Jetty8.
-
- Apr 26, 2012
-
-
kytv authored
-
- Mar 04, 2012
-
-
kytv authored
Work is needed so that I2P is built using jetty packages from Debian/Ubuntu.
-
- Feb 27, 2012
-
-
kytv authored
-
- Jan 04, 2012
-
-
kytv authored
-
- Jan 01, 2012
-
-
kytv authored
-
- Oct 08, 2011
-
-
kytv authored
-
- Aug 18, 2011
- Aug 09, 2011
-
-
kytv authored
installed by default if a JRE isn't installed yet. Since the packages previously depended on "default-jre|java5-runtime|java6-runtime", an already-installed headless package would have satisfied the dependency.
-
- Jun 22, 2011
-
-
kytv authored
GnewSense. This change will break nothing since we check for the existence of the lsb function files in the initscript. With an older version of lsb-base (like the one that came with Hardy (and GnewSense uses), the output from the initscript will simply look a little different (but again, nothing will break). Virtually everything but GnewSense comes with the desired lsb-base package anyway...
-
- Jun 13, 2011
-
-
kytv authored
-
- May 27, 2011
-
-
kytv authored
This commit splits the i2p package into a second package, i2p-router. * The new 'i2p-router' package does not depend on the java-wrapper nor jbigi. Jbigi is recommended. This package can be installed on the ports or distributions that the java-wrapper is not available for. * The new 'i2p' package depends on i2p-router, libjbigi-jni, and the java-wrapper. This package will add the i2psvc system user and the initscript. Existing users of the i2p package will have the i2p-router package pulled in automatically and for them there will be no usability changes. Executive summary: No functionality changes will take place for either those that installed the i2p package in the past or those that install the newly split i2p package. For them, "The Song Remains the Same."
-
- May 26, 2011
-
-
kytv authored
-
- May 25, 2011
-
-
kytv authored
-
- Nov 15, 2010
-
-
HungryHobo authored
-
- Nov 14, 2010
-
-
HungryHobo authored
-
- Nov 12, 2010
-
-
HungryHobo authored
-
HungryHobo authored
Make separate i386 and amd64 packages, this fixes the arch-independent-package-contains-binary-or-object lintian error
-
- Nov 10, 2010
-
-
HungryHobo authored
* Add dependency on libc6 which fixes the lintian warning missing-dependency-on-libc
-
- Oct 31, 2010
-
-
HungryHobo authored
-
- Jan 26, 2010
-
-
zzz authored
* build.xml: Speed up sponge's distclean additions
-
- Jan 30, 2009
-
-
dream authored
This sets i2p up as a functional Debian source package. dpkg-buildpackage will build i2p using ant preppkg (tarball takes too long and not helpful). It creates a binary .deb archive of the i2p installation, which when installed goes into /var/lib/i2p as the non-root user i2p, and adds an /etc/init.d script to start it up. Some problems not yet solved: 1) under Debian the conf should go into /etc/i2p, but since it doesn't things like the eepsite index file get overwritten if you reinstall. should check for those somehow and not replace them, or ask the user. 2) under Debian they like it if you split the generated data from the static code, so i2p should go into /usr/lib/i2p maybe, but its netDB and any other cache files into /var/cache/i2p that's important not just for organization, but also /var is often on a filesystem optimized for churn. For now just put it in /var/lib 3) i2p is supposedly architecture independant, but it does choose a native jbigi library on postinstall, so does that really count as architecture independant?
-