On Tue, May 20, 2003 at 06:19:00PM -0400, Morgon Kanter wrote:
> I've been looking to take over the orphaned package vtun (and am nearly
> complete packaging it. It has a number of autotools issues that need to
> be addressed still). However, I noticed that it is a non-US package.
>
> I'm wonde
I've been looking to take over the orphaned package vtun (and am nearly
complete packaging it. It has a number of autotools issues that need to
be addressed still). However, I noticed that it is a non-US package.
I'm wondering if this is exactly a problem, because I live in the US.
Can I simpl
On Tue, May 20, 2003 at 06:54:45PM +0100, Roger Leigh wrote:
> [EMAIL PROTECTED] writes:
> > libexecdir='${exec_prefix}/lib/${PACKAGE}'
>
> That's evil. The whole point of configure is to have install
> locations standardised, and changing the defaults is never, ever, a
> good idea.
The probl
[EMAIL PROTECTED] writes:
> The short version: Are these locations ok?
>
> /usr/lib/ -- helper scripts as part of a binary package
> /usr/lib//perl -- support modules for the helper scripts
Yes, but I think dumping things that aren't libraries in $prefix/lib
is using it like a rubbish
On Tue, May 20, 2003 at 02:48:08PM -0500, Graham Wilson wrote:
> Package: tdl
oops. the sujbect should be
Subject: RFS: tdl -- todo list manager
--
gram
pgp2p0D5n9MUk.pgp
Description: PGP signature
Package: tdl
Version: 1.4-1
Homepage: http://www.rrbcurnow.freeuk.com/tdl/
Deb: http://decoy.wox.org/~bob/debian/unstable/
NM-Status: waiting on DAM
Description: todo list manager
tdl is a program for managing a 'to-do' list of pending jobs that you
have.
.
Besides basic features like adding ne
I'm updating our build system for a package and (as a Debian user) I'm
trying to keep to Debian standards for installation locations. Again, this
is for Swish-e, which includes a binary program but also some helper
scripts.
I discussed this on the autoconf and automake lists, but also want to che
In message <[EMAIL PROTECTED]> yo
u write:
> On Tue, 20 May 2003, [iso-8859-1] Jörgen Hägg wrote:
>
> Have you considered /usr/share//cgi-bin and
> /usr/share//html and adding the necessary bits for Apache (and
> derivatives), and possibly any other webserver which users mention? There's
> pretty
On Tue, 20 May 2003, [iso-8859-1] J?rgen H?gg wrote:
> In message <[EMAIL PROTECTED]> yo
> u write:
>
> > What I am wondering is, apart from a webapp (which can afford the overhead
> > of scripting required to support inserting bits and bobs into webservers),
> > what sort of packages need to put
In message <[EMAIL PROTECTED]> yo
u write:
> What I am wondering is, apart from a webapp (which can afford the overhead
> of scripting required to support inserting bits and bobs into webservers),
> what sort of packages need to put webserver-accessible pages up?
That's exactly what it is, a web
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörgen,
On Tue, May 20, 2003 at 08:40:58AM +0200, Jörgen Hägg wrote:
> But if there are several programs with short names that may
> collide with other packages, is it ok to
> put them in /usr/lib/cgi-bin/package-name/?
Yes. Be sure to set the executa
On Tue, 20 May 2003, [iso-8859-1] J?rgen H?gg wrote:
> > Nooo. /usr/share/doc must be removable without any untoward
> > effects on the operation of the system. /usr/share/ is the
> > place to be, with an appropriate alias linking (probably)
> > http://localhost// to /usr/share/.
>
In message <[EMAIL PROTECTED]>
you write:
>
> Nooo. /usr/share/doc must be removable without any untoward
> effects on the operation of the system. /usr/share/ is the
> place to be, with an appropriate alias linking (probably)
> http://localhost// to /usr/share/.
Is there a standar
On Tue, 20 May 2003, [iso-8859-1] J?rgen H?gg wrote:
> Another question is where to put html-pages that the package uses.
> (Not documentation)
>
> /var/www seems to be a bad place, the only reasonable
> is /usr/share/doc/package-name/xyz.html or
> /usr/share/doc/package-name/html/xyz.html and re
I've been searching the policy for guidance about cgi-scripts.
The only thing I find is that they should be placed in /usr/lib/cgi-bin.
But if there are several programs with short names that may
collide with other packages, is it ok to
put them in /usr/lib/cgi-bin/package-name/?
Or would that b
On Sun, 18 May 2003, Geert Stappers wrote:
> > > So now I have a deb of it, anyone interested in sponsoring me? What do I
> > > do next?
> >
> > Keep pestering people until someone sponsors you.
>
> Ask at places where the package is used for a sponsor.
>
> Example given:
> You have package
16 matches
Mail list logo
