On Mon, Apr 05, 2004 at 04:12:30PM +0100, Tom Huckstep wrote:
> On Mon, Apr 05, 2004 at 03:43:51PM +0200, Frank K?ster wrote:
> > > 1. Add a Depends: on Python
> > > 2. Remove 'teepeedee-share' from the .deb
> > > 3. Put teepeedee-share in a separate package
> > > 4. Replace the 'teepeedee-share'
On Mon, Apr 05, 2004 at 12:57:55PM +, n.v.t n.v.t wrote:
> >Why? How big are the components? Would somebdy e.g install package-name
> >without package-icons or the other way round?
>
> It was a example. The person might only want the backgrounds or only the
> icons.
This alone is not suffic
On Mon, Apr 05, 2004 at 09:24:10AM +, n.v.t n.v.t wrote:
> Hello all.
>
> I have simple question which I could not find in the debian policy, maybe
> someone could point me out to that section or the right documentation? Or a
> explanation would be nice. I'm debianizing a package that I wou
On Sun, Apr 04, 2004 at 01:24:59PM +0200, Robert Ribnitz wrote:
> I am responsible for the package htdig. Htdig is a full-text indexer for
> (local) sites, ie. will generate a full-text (searchable) index of that
> site.
> The thing is written in C++, and comes with loads of libraries. While
>
Hi folks,
I'd like to upload konversation pretty soon. Matthew Palmer offered back in
December to do uploads, but I think he has become too busy, as I have
received no response to my latest email.
So, if someone here is willing to do a few uploads of this package, please let
me know. The pac
Hi folks,
I'd like to upload konversation pretty soon. Matthew Palmer offered back in
December to do uploads, but I think he has become too busy, as I have
received no response to my latest email.
So, if someone here is willing to do a few uploads of this package, please let
me know. The pac
On Monday 05 April 2004 20:57, Erik Bourget wrote:
> I'm wondering how to build multiple packages from a single source
Any specific problems?
Create two trees from debian/rules
(man dpkg-deb ! and related (man deb) !!).
You may want to do this using debhelper scripts (man debhelper, watch
out fo
On Mon, Apr 05, 2004 at 02:57:14PM -0400, Erik Bourget wrote:
>
> The new-maintainer faq seems to not go into this depth. Can anyone help me
> out with this one?
>
Just have a look to a multi-binary packages. You can find a lot of them around.
Basically you need to distinguish binary-dep and bi
* Erik Bourget ([EMAIL PROTECTED]) [040405 22:48]:
> I'm wondering how to build multiple packages from a single source tree,
> specifically:
>
> foobar : a daemon nominally called 'foobar'
> foobar-run : a daemontools/runit svdir for the daemon
>
> The new-maintainer faq seems to not go into this
On Monday 05 April 2004 14:31, Andreas Metzler wrote:
> On Mon, Apr 05, 2004 at 09:24:10AM +, WHAT'SYOURNAME wrote:
> > I'm debianizing a package that I would like to split up, like:
> > package-backgrounds
> > package-icons
> > package-examples
>
> Why? How big are the components? Would somebd
On Monday 05 April 2004 14:40, Bartosz Fenski aka fEnIo wrote:
> Is there any policy describing location of .desktop files?
> I've just checked Debian Policy, FHS and Developer's Reference, but
>
> I tried to check some packages to find how do they solve this issue,
> but now I'm really confused.
>
On Monday 05 April 2004 20:57, Erik Bourget wrote:
> I'm wondering how to build multiple packages from a single source
Any specific problems?
Create two trees from debian/rules
(man dpkg-deb ! and related (man deb) !!).
You may want to do this using debhelper scripts (man debhelper, watch
out fo
On Mon, Apr 05, 2004 at 02:57:14PM -0400, Erik Bourget wrote:
>
> The new-maintainer faq seems to not go into this depth. Can anyone help me
> out with this one?
>
Just have a look to a multi-binary packages. You can find a lot of them around.
Basically you need to distinguish binary-dep and bi
* Erik Bourget ([EMAIL PROTECTED]) [040405 22:48]:
> I'm wondering how to build multiple packages from a single source tree,
> specifically:
>
> foobar : a daemon nominally called 'foobar'
> foobar-run : a daemontools/runit svdir for the daemon
>
> The new-maintainer faq seems to not go into this
Hello;
I'm wondering how to build multiple packages from a single source tree,
specifically:
foobar : a daemon nominally called 'foobar'
foobar-run : a daemontools/runit svdir for the daemon
The new-maintainer faq seems to not go into this depth. Can anyone help me
out with this one?
Thanks,
On Monday 05 April 2004 14:31, Andreas Metzler wrote:
> On Mon, Apr 05, 2004 at 09:24:10AM +, WHAT'SYOURNAME wrote:
> > I'm debianizing a package that I would like to split up, like:
> > package-backgrounds
> > package-icons
> > package-examples
>
> Why? How big are the components? Would somebd
I'm sorry I forgot to give a example , the structure of the packge looks
like this:
dir/icon
dir/backgrounds
dir/examples
They all have a Makefile ofcourse in each directory.
Joe
_
Hotmail en Messenger on the move
http://www.m
Hi,
Ok, that seems to be all clear to me, what about the rules file? How do I
separate packages, the example that Andreas Metzler told me to check out,
doesn't clear things entirely. Is this the way we should learn it, by
examples? So I move files into a directory then create a deb out of each
On Monday 05 April 2004 14:40, Bartosz Fenski aka fEnIo wrote:
> Is there any policy describing location of .desktop files?
> I've just checked Debian Policy, FHS and Developer's Reference, but
>
> I tried to check some packages to find how do they solve this issue,
> but now I'm really confused.
>
Hi,
> Update: I've just tested the build on merulo.d.o (ia64), no problem
> there.
This is good news. Thanks to you and Aaron for trying this out.
> OTOH, you should really fix those warnings (the same ones
> you see when compiling on i386).
I fixed the compile warnings. But during debuild, d
I'm sorry I forgot to give a example , the structure of the packge looks
like this:
dir/icon
dir/backgrounds
dir/examples
They all have a Makefile ofcourse in each directory.
Joe
_
Hotmail en Messenger on the move
http://www.msn.n
Hi,
Ok, that seems to be all clear to me, what about the rules file? How do I
separate packages, the example that Andreas Metzler told me to check out,
doesn't clear things entirely. Is this the way we should learn it, by
examples? So I move files into a directory then create a deb out of each
On Mon, Apr 05, 2004 at 06:11:57PM +0300, Fabian Fagerholm wrote:
> On Mon, 2004-04-05 at 14:55, n.v.t n.v.t wrote:
> > What does the ${shlibs:Depends}, ${misc:Depends} mean? I can't find the
> > meaning of those in the debian policy either? Why not just put depends of
> > the splited package in
On Mon, Apr 05, 2004 at 05:17:47PM +0200, GCS wrote:
> I am applied[1] for a Debian Developer role, but as I see, Front Desk
> is stalling; I can't see any progress on applicants who have been
> advocated. So I have a couple of questions:
> - may I hope that Front Desk will assign an AM to me bef
Hi,
I am applied[1] for a Debian Developer role, but as I see, Front Desk
is stalling; I can't see any progress on applicants who have been
advocated. So I have a couple of questions:
- may I hope that Front Desk will assign an AM to me before Sarge is
released? (IMHO not :( ).
- is it ok that
On Mon, Apr 05, 2004 at 03:43:51PM +0200, Frank Küster wrote:
> > 1. Add a Depends: on Python
> > 2. Remove 'teepeedee-share' from the .deb
> > 3. Put teepeedee-share in a separate package
> > 4. Replace the 'teepeedee-share' with a shell wrapper, which calls the
> > script
> >if Python exists
Hi,
> Update: I've just tested the build on merulo.d.o (ia64), no problem
> there.
This is good news. Thanks to you and Aaron for trying this out.
> OTOH, you should really fix those warnings (the same ones
> you see when compiling on i386).
I fixed the compile warnings. But during debuild, d
On Mon, 2004-04-05 at 14:55, n.v.t n.v.t wrote:
> What does the ${shlibs:Depends}, ${misc:Depends} mean? I can't find the
> meaning of those in the debian policy either? Why not just put depends of
> the splited package in the depends line instead of this?
You can manually enter the dependencies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2004-04-05 14:40, Bartosz Fenski aka fEnIo wrote:
> Hello.
>
> Is there any policy describing location of .desktop files?
> I've just checked Debian Policy, FHS and Developer's Reference, but
> I couldn't find anything related to these files. Maybe
On Mon, Apr 05, 2004 at 06:11:57PM +0300, Fabian Fagerholm wrote:
> On Mon, 2004-04-05 at 14:55, n.v.t n.v.t wrote:
> > What does the ${shlibs:Depends}, ${misc:Depends} mean? I can't find the
> > meaning of those in the debian policy either? Why not just put depends of
> > the splited package in
Tom Huckstep <[EMAIL PROTECTED]> wrote:
> It's a small package which contains a Python "helper" script
> 'teepeedee-share' to help with a basic configuration. As far as I can tell,
> I have the following options:
>
> 1. Add a Depends: on Python
> 2. Remove 'teepeedee-share' from the .deb
> 3. Put
On Mon, Apr 05, 2004 at 05:17:47PM +0200, GCS wrote:
> I am applied[1] for a Debian Developer role, but as I see, Front Desk
> is stalling; I can't see any progress on applicants who have been
> advocated. So I have a couple of questions:
> - may I hope that Front Desk will assign an AM to me bef
Hi,
I am applied[1] for a Debian Developer role, but as I see, Front Desk
is stalling; I can't see any progress on applicants who have been
advocated. So I have a couple of questions:
- may I hope that Front Desk will assign an AM to me before Sarge is
released? (IMHO not :( ).
- is it ok that
On Mon, Apr 05, 2004 at 03:43:51PM +0200, Frank Küster wrote:
> > 1. Add a Depends: on Python
> > 2. Remove 'teepeedee-share' from the .deb
> > 3. Put teepeedee-share in a separate package
> > 4. Replace the 'teepeedee-share' with a shell wrapper, which calls the script
> >if Python exists
> [.
On Mon, 2004-04-05 at 14:55, n.v.t n.v.t wrote:
> What does the ${shlibs:Depends}, ${misc:Depends} mean? I can't find the
> meaning of those in the debian policy either? Why not just put depends of
> the splited package in the depends line instead of this?
You can manually enter the dependencies
From: Andreas Metzler <[EMAIL PROTECTED]>
Reply-To: debian-mentors@lists.debian.org, [EMAIL PROTECTED]
To: debian-mentors@lists.debian.org
CC: [EMAIL PROTECTED]
Subject: Re: Separating packages.
Date: Mon, 5 Apr 2004 14:31:43 +0200
On Mon, Apr 05, 2004 at 09:24:10AM +, n.v.t n.v.t wrote:
I've got a package of teepeedee[1] shortly arriving in Debian via a sponsor.
It's a small package which contains a Python "helper" script
'teepeedee-share' to help with a basic configuration. As far as I can tell,
I have the following options:
1. Add a Depends: on Python
2. Remove 'teepeedee-sh
Hello.
I'm looking for sponsor for package otak.
It's a visual interface for commandline programs. It can be used as
abook replacement if you use it with mutt, but it's not limited only to
that application.
Here goes relevant information:
* Package name: otak
Version : 1.3.4
Ups
On Mon, 2004-04-05 at 05:53, Rudy Godoy wrote:
> Hi, just to announce that TORCS[0] Debian package[1] is ready for testing,
Cool, no more messing with CVS. :)
> you can grab it from mentors[2]. There is a i396 package and the sources, if
> you are
> going to compile it, I encourage you to use l
Hello.
Is there any policy describing location of .desktop files?
I've just checked Debian Policy, FHS and Developer's Reference, but
I couldn't find anything related to these files. Maybe I searched
wrongly, then tell me where can I find it.
I tried to check some packages to find how do they sol
On Mon, Apr 05, 2004 at 09:24:10AM +, n.v.t n.v.t wrote:
> I have simple question which I could not find in the debian policy, maybe
> someone could point me out to that section or the right documentation? Or a
> explanation would be nice. I'm debianizing a package that I would like to
> spl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2004-04-05 14:40, Bartosz Fenski aka fEnIo wrote:
> Hello.
>
> Is there any policy describing location of .desktop files?
> I've just checked Debian Policy, FHS and Developer's Reference, but
> I couldn't find anything related to these files. Maybe
From: Fabian Fagerholm <[EMAIL PROTECTED]>
To: "n.v.t n.v.t" <[EMAIL PROTECTED]>
CC: debian-mentors@lists.debian.org
Subject: Re: Separating packages.
Date: 05 Apr 2004 13:05:45 +0300
On Mon, 2004-04-05 at 12:24, n.v.t n.v.t wrote:
> package-backgrounds
> package-icons
> package-examples
> pa
Tom Huckstep <[EMAIL PROTECTED]> wrote:
> It's a small package which contains a Python "helper" script
> 'teepeedee-share' to help with a basic configuration. As far as I can tell,
> I have the following options:
>
> 1. Add a Depends: on Python
> 2. Remove 'teepeedee-share' from the .deb
> 3. Put
From: Andreas Metzler <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: Separating packages.
Date: Mon, 5 Apr 2004 14:31:43 +0200
On Mon, Apr 05, 2004 at 09:24:10AM +, n.v.t n.v.t wrote:
> I have simple question which
I've got a package of teepeedee[1] shortly arriving in Debian via a sponsor.
It's a small package which contains a Python "helper" script
'teepeedee-share' to help with a basic configuration. As far as I can tell,
I have the following options:
1. Add a Depends: on Python
2. Remove 'teepeedee-sh
Hello.
I'm looking for sponsor for package otak.
It's a visual interface for commandline programs. It can be used as
abook replacement if you use it with mutt, but it's not limited only to
that application.
Here goes relevant information:
* Package name: otak
Version : 1.3.4
Ups
On Mon, 2004-04-05 at 05:53, Rudy Godoy wrote:
> Hi, just to announce that TORCS[0] Debian package[1] is ready for testing,
Cool, no more messing with CVS. :)
> you can grab it from mentors[2]. There is a i396 package and the sources, if you are
> going to compile it, I encourage you to use libf
Hello.
Is there any policy describing location of .desktop files?
I've just checked Debian Policy, FHS and Developer's Reference, but
I couldn't find anything related to these files. Maybe I searched
wrongly, then tell me where can I find it.
I tried to check some packages to find how do they sol
On Mon, Apr 05, 2004 at 09:24:10AM +, n.v.t n.v.t wrote:
> I have simple question which I could not find in the debian policy, maybe
> someone could point me out to that section or the right documentation? Or a
> explanation would be nice. I'm debianizing a package that I would like to
> spl
From: Fabian Fagerholm <[EMAIL PROTECTED]>
To: "n.v.t n.v.t" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: Separating packages.
Date: 05 Apr 2004 13:05:45 +0300
On Mon, 2004-04-05 at 12:24, n.v.t n.v.t wrote:
> package-backgrounds
> package-icons
> package-examples
> package-name (which
On Mon, 2004-04-05 at 12:24, n.v.t n.v.t wrote:
> package-backgrounds
> package-icons
> package-examples
> package-name (which contains all of the above) Should I do this as a
> meta-package? How do I create a meta-package?
I don't think you need a meta package. I would do this to allow
flexibili
Hello all.
I have simple question which I could not find in the debian policy, maybe
someone could point me out to that section or the right documentation? Or a
explanation would be nice. I'm debianizing a package that I would like to
split up in several parts, the package has a 'backgrounds'
On Mon, 2004-04-05 at 12:24, n.v.t n.v.t wrote:
> package-backgrounds
> package-icons
> package-examples
> package-name (which contains all of the above) Should I do this as a
> meta-package? How do I create a meta-package?
I don't think you need a meta package. I would do this to allow
flexibili
Hello all.
I have simple question which I could not find in the debian policy, maybe
someone could point me out to that section or the right documentation? Or a
explanation would be nice. I'm debianizing a package that I would like to
split up in several parts, the package has a 'backgrounds' d
55 matches
Mail list logo
