Re: init script

>> "MM" == Mauro Mazzieri <[EMAIL PROTECTED]> writes: MM> 1) The program must be started as: MM> # udplog MM> where level is a number. No default is read from is config file. Is MM> 2) Non all the user would like to start the command from init. So MM> there must a postinst script that ask the u

Re: [HOWTO?] Splitting one upstream package into several .debs

Josip Rodin wrote: > On Thu, Feb 11, 1999 at 01:56:24PM -0800, Sudhakar Chandrasekharan wrote: > > But I want to build a total of four packages - aspell (containing the > > binaries), libaspell0 (containing the libraries), libaspell-dev (containing > > the header files) and aspell-doc (containg the

Re: [HOWTO?] Splitting one upstream package into several .debs

On Thu, Feb 11, 1999 at 01:56:24PM -0800, Sudhakar Chandrasekharan wrote: > > > W: libaspell0: non-dev-pkg-with-shlib-symlink usr/lib/libaspell.so.0.0.0 > > > usr/lib/libaspell.so > > > usr/lib/libaspell.so.0.0.0 > > > usr/lib/libaspell.so -> libaspell.so.0.0.0 > > > > Simply, make this libaspell.

Re: packaging from root account

In foo.debian-mentors, you wrote: > I use root account to debianize a package and to exec all the scripts, > except lintian. Is it wrong? Or is better to use my ordinary account and > give it write permission on /usr/local? I would _not_ package as root. You can give yourself permissions in a sub

Re: [HOWTO?] Splitting one upstream package into several .debs

Josip Rodin wrote: > On Thu, Feb 11, 1999 at 12:19:26PM -0800, Sudhakar Chandrasekharan wrote: > > W: libaspell0: non-dev-pkg-with-shlib-symlink usr/lib/libaspell.so.0.0.0 > > usr/lib/libaspell.so > > usr/lib/libaspell.so.0.0.0 > > usr/lib/libaspell.so -> libaspell.so.0.0.0 > > Simply, make this l

init script

I'm packaging an udp logger. I would like to make it start from init, but I have some little problems. 1) The program must be started as: # udplog where level is a number. No default is read from is config file. Is right to hardcode the level in the init script? Or the level must be read from a f

packaging from root account

I use root account to debianize a package and to exec all the scripts, except lintian. Is it wrong? Or is better to use my ordinary account and give it write permission on /usr/local? -- Mauro Mazzieri - http://gulliver.unian.it/~mazzieri/ finger [EMAIL PROTECTED] for PGP key and geek code I P

Re: [HOWTO?] Splitting one upstream package into several .debs

On Thu, Feb 11, 1999 at 12:19:26PM -0800, Sudhakar Chandrasekharan wrote: > W: libaspell0: non-dev-pkg-with-shlib-symlink usr/lib/libaspell.so.0.0.0 > usr/lib/libaspell.so > usr/lib/libaspell.so.0.0.0 > usr/lib/libaspell.so -> libaspell.so.0.0.0 Simply, make this libaspell.so go into the libaspell

Re: [HOWTO?] Splitting one upstream package into several .debs

Sudhakar Chandrasekharan wrote: > I have not yet uploaded my packages. My packages are available from > http://www.aunet.org/thaths/hacks/deb/aspell/ Would appreciate if you > folks took a look and told me if things are OK for an upload. I have made some progress since that. Lintian used to com

Re: [HOWTO?] Splitting one upstream package into several .debs

On Wed, 10 Feb, 1999, Sudhakar Chandrasekharan wrote: > Edward Betts wrote: > > On Wed, 03 Feb, 1999, Sudhakar Chandrasekharan wrote: > > > Thanks for all the help guys. I am now packaging aspell into aspell.deb, > > > aspell-dev.deb and aspell-doc.deb Should all of them go into the same > > liba

Unstripped library

For GNAT (the GNU Ada95 compiler), we need to have a dynamic library installed with debugging symbols, as those symbols are used for traceback information when an exception is raised. Also, many utilities use the debugging information to help people develop their Ada programs. How is it possible t