--- Robert Bihlmeyer <[EMAIL PROTECTED]> wrote: >
Michèl Alexandre Salim <[EMAIL PROTECTED]>
> writes:
>
> [your mail formatting was totally messed up, BTW]
>
Yes, sorry about that :) Using the university's
network connection to do most of my e-mailing and
somehow or another it is fraught with p
On Mon, 04 Jun 2001, Jason Thomas wrote:
> hmmm, I just had the upstream remove the debian specific stuff so I
> could have policy compilant stuff and use the debhelper stuff more.
I also did the same in fetchmail. It gets easier to maintain a package that
has no debian/ directory (which is often
hmmm, I just had the upstream remove the debian specific stuff so I
could have policy compilant stuff and use the debhelper stuff more.
On Mon, Jun 04, 2001 at 03:14:20AM +0100, Mich?l Alexandre Salim wrote:
> Hello,
>
> A general observation of Unix programs in general - a
> lot more of them com
Hello,
A general observation of Unix programs in general - a
lot more of them come with RPM spec files, even
generates them automatically from a spec.in file, than
with debian scripts.
Probably a function of the majority of Linux users /
programmers working on RPM-based systems but I am
curious a
Steve Langasek wrote:
> /usr/share/doc/, not /usr/share/. Two different beasts.
Ah indeed. Then you're right of course. Sorry.
--
see shy jo
On Mon, 04 Jun 2001, Jason Thomas wrote:
> hmmm, I just had the upstream remove the debian specific stuff so I
> could have policy compilant stuff and use the debhelper stuff more.
I also did the same in fetchmail. It gets easier to maintain a package that
has no debian/ directory (which is often
hmmm, I just had the upstream remove the debian specific stuff so I
could have policy compilant stuff and use the debhelper stuff more.
On Mon, Jun 04, 2001 at 03:14:20AM +0100, Mich?l Alexandre Salim wrote:
> Hello,
>
> A general observation of Unix programs in general - a
> lot more of them co
Hello,
A general observation of Unix programs in general - a
lot more of them come with RPM spec files, even
generates them automatically from a spec.in file, than
with debian scripts.
Probably a function of the majority of Linux users /
programmers working on RPM-based systems but I am
curious
On Sun, 3 Jun 2001, Joey Hess wrote:
> Julian Gilbey wrote:
> > Agreed. (And I don't think /usr/share/ is mandated.)
> Every package MUST be accompanied by a verbatim copy of its copyright
> and distribution license in the file
> `/usr/share/doc/__/copyright'
> Packages that
Julian Gilbey wrote:
> Agreed. (And I don't think /usr/share/ is mandated.)
Every package MUST be accompanied by a verbatim copy of its copyright
and distribution license in the file
`/usr/share/doc/__/copyright'
Packages that are not Debian-native MUST contain a copy of
Colin Watson wrote:
> Muhammad Hussain Yusuf <[EMAIL PROTECTED]> wrote:
> >I have a package, gstar, which places various lists of stars in
> >/usr/share/starchart since gstar is a gtk front-end to the starchart
> >programme.
> >
> >My question is: is there any policy or guidelines about naming stuf
On Sun, Jun 03, 2001 at 11:26:24PM +0100, Colin Watson wrote:
> Muhammad Hussain Yusuf <[EMAIL PROTECTED]> wrote:
> >I have a package, gstar, which places various lists of stars in
> >/usr/share/starchart since gstar is a gtk front-end to the starchart
> >programme.
> >
> >My question is: is there
On Sun, Jun 03, 2001 at 02:37:19PM +0200, Russell Coker wrote:
> Also make the package check for the presence of the character device
> /dev/.devfsd first, if that device exists then your script must not attempt
> to create the device node and it should be left for the kernel to do it! If
> you
Steve Langasek wrote:
> /usr/share/doc/, not /usr/share/. Two different beasts.
Ah indeed. Then you're right of course. Sorry.
--
see shy jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Muhammad Hussain Yusuf <[EMAIL PROTECTED]> wrote:
>I have a package, gstar, which places various lists of stars in
>/usr/share/starchart since gstar is a gtk front-end to the starchart
>programme.
>
>My question is: is there any policy or guidelines about naming stuff in
>in /usr/share?
/usr/share
On Wed, May 02, 2001 at 09:59:08AM +0200, Robert Bihlmeyer wrote:
> "Steve M. Robbins" <[EMAIL PROTECTED]> writes:
>
> > Well, for starters, he said the software is "an official GNU project",
> > not something written specifically for Debian.
>
> "Debian native", does, in my definition, not imply
On Sun, 3 Jun 2001, Joey Hess wrote:
> Julian Gilbey wrote:
> > Agreed. (And I don't think /usr/share/ is mandated.)
> Every package MUST be accompanied by a verbatim copy of its copyright
> and distribution license in the file
> `/usr/share/doc/__/copyright'
> Packages tha
Julian Gilbey wrote:
> Agreed. (And I don't think /usr/share/ is mandated.)
Every package MUST be accompanied by a verbatim copy of its copyright
and distribution license in the file
`/usr/share/doc/__/copyright'
Packages that are not Debian-native MUST contain a copy of
Colin Watson wrote:
> Muhammad Hussain Yusuf <[EMAIL PROTECTED]> wrote:
> >I have a package, gstar, which places various lists of stars in
> >/usr/share/starchart since gstar is a gtk front-end to the starchart
> >programme.
> >
> >My question is: is there any policy or guidelines about naming stu
On Sun, Jun 03, 2001 at 11:26:24PM +0100, Colin Watson wrote:
> Muhammad Hussain Yusuf <[EMAIL PROTECTED]> wrote:
> >I have a package, gstar, which places various lists of stars in
> >/usr/share/starchart since gstar is a gtk front-end to the starchart
> >programme.
> >
> >My question is: is there
On Sun, Jun 03, 2001 at 02:37:19PM +0200, Russell Coker wrote:
> Also make the package check for the presence of the character device
> /dev/.devfsd first, if that device exists then your script must not attempt
> to create the device node and it should be left for the kernel to do it! If
> yo
Muhammad Hussain Yusuf <[EMAIL PROTECTED]> wrote:
>I have a package, gstar, which places various lists of stars in
>/usr/share/starchart since gstar is a gtk front-end to the starchart
>programme.
>
>My question is: is there any policy or guidelines about naming stuff in
>in /usr/share?
/usr/shar
On Wed, May 02, 2001 at 09:59:08AM +0200, Robert Bihlmeyer wrote:
> "Steve M. Robbins" <[EMAIL PROTECTED]> writes:
>
> > Well, for starters, he said the software is "an official GNU project",
> > not something written specifically for Debian.
>
> "Debian native", does, in my definition, not impl
Michèl Alexandre Salim <[EMAIL PROTECTED]> writes:
[your mail formatting was totally messed up, BTW]
> Have not managed to package Pango - can anyone assist me in finding
> out what is going wrong? Basically the package failed the install
> stage of the rules script if installed using an alternat
Hi,
I have a package, gstar, which places various lists of stars in
/usr/share/starchart since gstar is a gtk front-end to the starchart
programme.
My question is: is there any policy or guidelines about naming stuff in
in /usr/share?
Should the dir be named /usr/share/gstar as that is the name o
On Sat, Jun 02, 2001 at 02:09:13PM +0200, Robert Bihlmeyer wrote:
> The usual way people do multiple binary packages is that debian/rules
> calls the package's install method with one target directory and then
> for each package, it moves this package's files from that directory
> into the package'
Michèl Alexandre Salim <[EMAIL PROTECTED]> writes:
[your mail formatting was totally messed up, BTW]
> Have not managed to package Pango - can anyone assist me in finding
> out what is going wrong? Basically the package failed the install
> stage of the rules script if installed using an alterna
Hi,
I have a package, gstar, which places various lists of stars in
/usr/share/starchart since gstar is a gtk front-end to the starchart
programme.
My question is: is there any policy or guidelines about naming stuff in
in /usr/share?
Should the dir be named /usr/share/gstar as that is the name
--- Ben Gertzfield <[EMAIL PROTECTED]> wrote: > > "Michel" == l Alexandre Salim writes:
>
> Michel> Hello, IANAD yet but wanting to get up
> to speed on the
> Michel> upcoming GNOME 2 platform, I wanted to
> start programming
> Michel> in Gtk+ 1.3.x / Inti. They are not
> availabl
--- Ben Gertzfield <[EMAIL PROTECTED]> wrote: > > "Michel" == l Alexandre Salim writes:
>
> Michel> Hello, IANAD yet but wanting to get up
> to speed on the
> Michel> upcoming GNOME 2 platform, I wanted to
> start programming
> Michel> in Gtk+ 1.3.x / Inti. They are not
> availabl
On Sat, Jun 02, 2001 at 02:09:13PM +0200, Robert Bihlmeyer wrote:
> The usual way people do multiple binary packages is that debian/rules
> calls the package's install method with one target directory and then
> for each package, it moves this package's files from that directory
> into the package
--- Ben Gertzfield <[EMAIL PROTECTED]> wrote: > > "Michel" == l Alexandre Salim writes:
>
> Michel> Hello, IANAD yet but wanting to get up
> to speed on the
> Michel> upcoming GNOME 2 platform, I wanted to
> start programming
> Michel> in Gtk+ 1.3.x / Inti. They are not
> availabl
--- Ben Gertzfield <[EMAIL PROTECTED]> wrote: > > "Michel" == l Alexandre Salim writes:
>
> Michel> Hello, IANAD yet but wanting to get up
> to speed on the
> Michel> upcoming GNOME 2 platform, I wanted to
> start programming
> Michel> in Gtk+ 1.3.x / Inti. They are not
> availabl
On Sunday 03 June 2001 11:36, Richard Atterer wrote:
> On Sun, Jun 03, 2001 at 01:01:15PM +0530, Viral wrote:
> > intel-rng-tools requires /dev/intel_rng, which is not installed by
> > makedev. I believe its not a good idea to use mknod in the postinst
> > scripts. How would I go about doing this t
On Sunday 03 June 2001 11:36, Richard Atterer wrote:
> On Sun, Jun 03, 2001 at 01:01:15PM +0530, Viral wrote:
> > intel-rng-tools requires /dev/intel_rng, which is not installed by
> > makedev. I believe its not a good idea to use mknod in the postinst
> > scripts. How would I go about doing this
On Sun, Jun 03, 2001 at 01:01:15PM +0530, Viral wrote:
> intel-rng-tools requires /dev/intel_rng, which is not installed by
> makedev. I believe its not a good idea to use mknod in the postinst
> scripts. How would I go about doing this then ?
>
> Currently, its just an instruction in README.Debia
Hi,
intel-rng-tools requires /dev/intel_rng, which is not installed by makedev.
I believe its not a good idea to use mknod in the postinst scripts.
How would I go about doing this then ?
Currently, its just an instruction in README.Debian.
Thanks,
viral
--
"Live for today, gone tomorrow, that
On Sun, Jun 03, 2001 at 01:01:15PM +0530, Viral wrote:
> intel-rng-tools requires /dev/intel_rng, which is not installed by
> makedev. I believe its not a good idea to use mknod in the postinst
> scripts. How would I go about doing this then ?
>
> Currently, its just an instruction in README.Debi
Hi,
intel-rng-tools requires /dev/intel_rng, which is not installed by makedev.
I believe its not a good idea to use mknod in the postinst scripts.
How would I go about doing this then ?
Currently, its just an instruction in README.Debian.
Thanks,
viral
--
"Live for today, gone tomorrow, tha
39 matches
Mail list logo
