Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:1

Slash as Debian Package

posted by Krow on 02:10 PM December 18th, 2000   Printer-friendly   Email story
Bernd Eckenfels writes "I would like to turn slash into a Debian Package. I just posted the ITP Request (#79858) to the Debian List and will wait if anybody has objections. Has anybody done work on slash?

I intend to build a slash_1.1.0-1_i386.deb package soon.

I am not quite sure if I should name the package slash or slash1.1 since, as i understand it is a new codebase. But I doubt anybody wants tu run 1.0 and 1.1 on the same system? Will anybody want to install old versions one bender has become mature?


I wouldn't think they would. None of us has had the time to build a debian package yet (or RPM) but this is something we would like to start giving out during the beta. So, if someone can automate either of these, we will probably at it to the ditribution.

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • Guess what?! I am Happy to announce the Version -2 which now will geneate a slash Group and User. It will Fix up all Permissions of the involved Files, it will even add www-date to the slash Group (to allow Read Access to The Stuff which is still mising is installing/upgrading the Database and Installing the Hooks into apache's config file. You should also be sure to actually activate libapache-mod-perl, since this Debian Package wont actively configure the Module to load.

    For Debugging pay special Attention to the Output of "tail /var/log/apache/error.log" and "tail /var/log/slash/slashd.log". The Former if you have Errors Accessing the Web Frontend Site ("internal Server Error...") the Later, if you feel like your site is not refreshing itself, at all.

    Hint: You can also start slashd from Shell, it will give you additional Output. Make sure you su to User slash first. In case you forgot to su to slash, use slash_fixperms, just to be sure the permissions on log files, cached index files or pid files are ok.

    Hint2: This PAckage does require Woody and perl-5.6. You should pay special Attention to your /usr/bin/perl Link after upgrading to perl-5.6. If it is pointing to an old Perl Version, it will break some of your System.

  • Hello,

    I am happy to announce the first Version of a Debian Package for slash 1.0.9.

    Unfortunatelly I was not able to get 1.1.x to run, so I start with the stable Version of Slash, which was easy to set up. I tweaked the code a lot to fit into the FHS, and now the packages are ready. 2 Major points are missing: load the database, generate the user and tweak the config templates (did I say 2?).

    Well.. get it while it is hot:

    1. Add the following lines to /etc/apt/sources.list
      deb i386/
      deb all/
    2. apt-get -ufm install slash

    NOTE: it requires a lot additional packages but all of them are included in Debian 'Woody'.

    Please make sure to read the README.Debian File in the /usr/share/doc/slash/ dir.

    In case you are curious, here is the Link to the diff:

    diff.gz []

  • by Anonymous Coward
    well, last time I checked, most of them were already debianized. also, i'm underway packaging more of them
  • by Anonymous Coward
    Is it against Debian guidelines not to explicit dependecies for perl modules but just instruct the user to install by himself?

    Too hard :)

    I've tried to install slashcode once, and I won't bother again unless there's a really easy way. I know nothing about Perl, but I can figure out that something was broken in a lot of modules I downloaded and it didn't work.

    If all the modules are packaged and i can run "apt-get install slashcode" then it will make it a lot easier for a perl newbie to set it up :)
  • just try "apt-get install slash" this will solve all the perl dependecy stuff.
  • by Anonymous Coward
    One significant hurdle to creating such a deb will be the necessity of creating all the necessary perl module debs! Last time I checked nearly 1/2 of them had not been debianized.
  • Yes, I believe that's quite a problem. Also, lots of Perl developers want to keep an eye on latest releases of modules and usually the few that are packaged are not very updated.

    I am testing the Bender beta on a Debian box and I used packaged apache, perl, mod_perl, expat, but I installed all Perl modules via CPAN.

    Is it against Debian guidelines not to explicit dependecies for perl modules but just instruct the user to install by himself?

    "It is more complicated than you think" -- Th


    Check out the Slash in Italian Project []