Opened 5 years ago

Closed 5 years ago

#1310 closed task (fixed)

fix-up slackbuild

Reported by: killyourtv Owned by: killyourtv
Priority: maintenance Milestone: 0.9.14
Component: package/slackware Version: 0.9.13
Keywords: Cc:
Parent Tickets:

Description (last modified by killyourtv)

Apparently, when making a slackware package using our included slackbuild scripts, i2prouter is configured to run I2P as root. Of course, this means running i2prouter start as a normal user will fail.

This ticket has been created to make sure that this, amongst other issues, gets taken care of.

Since sponge is on extended AFK, I'm assigning this to myself.

Subtickets

Change History (2)

comment:1 Changed 5 years ago by killyourtv

  • Description modified (diff)

comment:2 Changed 5 years ago by killyourtv

  • Milestone changed from 0.9.15 to 0.9.14
  • Resolution set to fixed
  • Status changed from new to closed

Fixed in efdac4a5fc1330f0ff4c837f38efbb7941d7ba56.

Now the SlackBuild?

  • is less convoluted
  • doesn't require bash
  • has tidier regexes
  • has error checking throughout (data loss is bad)
  • doesn't assume pwd and dirname $0 are the same (data loss is bad)
  • doesn't warn about updated files that are identical to the already existing ones
  • doesn't sound the system bell 14 times (!) when the initscript is installed (whether it's identical to the existing one or not)
  • works with x64 JREs
  • doesn't run from the initscript as root
  • doesn't require root access to run i2prouter
  • doesn't require i2prouter to be edited in order to run I2P
  • installs manpages
  • installs licenses, readme, and changelog to docs directory
  • has updated docs
Note: See TracTickets for help on using tickets.