Hi Ali,
Ali Mezgani writes:
> Hello,
>
> What is the issue, if you need a new contributor I should do. What are
> blocking phases?
>
Sorry, I missed your email and don't understand what you mean. Do you
mean you'd like to package the "New Session Manager" fork (fltk port)?
Thanks,
Nicholas
Hi,
"rosea.grammostola" writes:
> To be more precise: non-session-manager is forked. That fork
> (new-session-manager) can be build without NTK.
>
> Non-Daw with non-sequencer/non-timeline/non-mixer isn't forked and still
> needs the NTK toolkit (fork of fltk).
>
Hmm, maybe I should prioritis
Hi Rosea,
"rosea.grammostola" writes:
> Project has been forked, I've no interest in packaging it, but it should
> be easier now with plain FLTK instead of NTK
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965068
>
Thank you for the link. Yes, and with meson replacing the waf evil :-)
To be more precise: non-session-manager is forked. That fork
(new-session-manager) can be build without NTK.
Non-Daw with non-sequencer/non-timeline/non-mixer isn't forked and still
needs the NTK toolkit (fork of fltk).
On 7/21/20 7:14 PM, rosea.grammostola wrote:
Project has been forked, I'v
Project has been forked, I've no interest in packaging it, but it should
be easier now with plain FLTK instead of NTK
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965068
On 7/21/20 6:23 PM, Nicholas D Steeves wrote:
Hi Rosea,
Sorry for the long delay in replying. I lost the thread and i
Hello,
What is the issue, if you need a new contributor I should do. What are
blocking phases?
Regards,
On Tue, Jul 21, 2020 at 17:24 Nicholas D Steeves wrote:
> Hi Rosea,
>
> Sorry for the long delay in replying. I lost the thread and it took me
> this long to think "say, I wonder what happe
Hi Rosea,
Sorry for the long delay in replying. I lost the thread and it took me
this long to think "say, I wonder what happened with that new
contributor who wants to work on NON?"
"rosea.grammostola" writes:
> Nicholas and others,
>
> Ha, I didn't solve anything man. I'm probably the most un
On Mon, Mar 09, 2020 at 09:35:17PM +0100, rosea.grammostola wrote:
> > > If you just want to package non-session-manager, why not:
> > > 1. Download the tarball from here:
> > > https://git.tuxfamily.org/non/non.git/tag/?id=non-session-manager-v1.2.0
> > > (or the github mirror - whichever is best)
On Mon, Mar 09, 2020 at 11:02:03PM +0100, rosea.grammostola wrote:
> > how did you
> > resolve the NTK-fork dep and the waf evil?
>
> About he Waf evil, upstream developer told me this:
>
> "There was an issue a while I ago that I fixed related to how unique the
> shipped WAF binary is. I think i
On Mon, Mar 09, 2020 at 03:11:04PM -0600, Nicholas D Steeves wrote:
> src:non (or src:non-daw) would generate
> bin:non-{timeline,sequencer,mixer,session-manager}. Andrey, is the
> simplest method still debian/bin-pkg-name0.install and
> debian/bin-pkg-name1.install + simple glob patterns, and/or
On 3/9/20 10:11 PM, Nicholas D Steeves wrote:
how did you
resolve the NTK-fork dep and the waf evil?
About he Waf evil, upstream developer told me this:
"There was an issue a while I ago that I fixed related to how unique the
shipped WAF binary is. I think it should be in a good place now t
Nicholas and others,
Ha, I didn't solve anything man. I'm probably the most unclassified
person for the job. But hey, if no one wants to do it, you've to do it
yourself isn't it? Which I can't so that's why I'm asking these 'stupid'
newbie questions on this list. Sure there are all kind of obs
Hi,
Rosea, thank you for working on Non! Out of curiosity, how did you
resolve the NTK-fork dep and the waf evil? If it wouldn't be too much
trouble, would you please generate bin packages for the full suite? I'm
personally interested in the Timeline, Mixer, and Session manager, and I
have a fr
On 3/9/20 9:30 PM, Andrey Rahmatullin wrote:
On Mon, Mar 09, 2020 at 08:58:26PM +0100, Ross Gammon wrote:
If you just want to package non-session-manager, why not:
1. Download the tarball from here:
https://git.tuxfamily.org/non/non.git/tag/?id=non-session-manager-v1.2.0
(or the github mirror
On Mon, Mar 09, 2020 at 08:58:26PM +0100, Ross Gammon wrote:
> If you just want to package non-session-manager, why not:
> 1. Download the tarball from here:
> https://git.tuxfamily.org/non/non.git/tag/?id=non-session-manager-v1.2.0
> (or the github mirror - whichever is best)
That's just a snapsho
Hi Rosea,
On 09/03/2020 16:37, Andrey Rahmatullin wrote:
> On Mon, Mar 09, 2020 at 03:20:26PM +0100, rosea.grammostola wrote:
>>> You just need to create a source tarball that is able to build the project
>>> you need. For that you'll need to find out which common files are also
>>> needed.
>>> Yo
On Mon, Mar 09, 2020 at 03:20:26PM +0100, rosea.grammostola wrote:
> > You just need to create a source tarball that is able to build the project
> > you need. For that you'll need to find out which common files are also
> > needed.
> > You'll need to do it manually each time you need to upload a n
On 3/9/20 2:55 PM, Andrey Rahmatullin wrote:
You just need to create a source tarball that is able to build the project
you need. For that you'll need to find out which common files are also
needed.
You'll need to do it manually each time you need to upload a new version,
so I guess you'll want
On Mon, Mar 09, 2020 at 02:26:49PM +0100, rosea.grammostola wrote:
>
> On 3/9/20 2:11 PM, Andrey Rahmatullin wrote:
> > > You can build each project independently.
> > It doesn't matter.
> > If you are able to split this repo into separate source packages, do it,
> >
> That's probably the best op
On 3/9/20 2:11 PM, Andrey Rahmatullin wrote:
You can build each project independently.
It doesn't matter.
If you are able to split this repo into separate source packages, do it,
That's probably the best option then. But what if upstream doesn't want
to split it, how do I split it 'according
On Mon, Mar 09, 2020 at 01:07:34PM +0100, rosea.grammostola wrote:
> > > This git repo contains four packages, but I only want to package one. How
> > > to
> > > deal with this situation via git-buildpackage? (Upstream sources kept in
> > > the
> > > upstream branch and the the debian in the mast
On 3/9/20 12:56 PM, Andrey Rahmatullin wrote:
On Mon, Mar 09, 2020 at 11:18:04AM +0100, rosea.grammostola wrote:
Hi,
This git repo contains four packages, but I only want to package one. How to
deal with this situation via git-buildpackage? (Upstream sources kept in the
upstream branch and th
On Mon, Mar 09, 2020 at 11:18:04AM +0100, rosea.grammostola wrote:
> Hi,
>
> This git repo contains four packages, but I only want to package one. How to
> deal with this situation via git-buildpackage? (Upstream sources kept in the
> upstream branch and the the debian in the master branch)
>
> h
Hi,
This git repo contains four packages, but I only want to package one.
How to deal with this situation via git-buildpackage? (Upstream sources
kept in the upstream branch and the the debian in the master branch)
https://git.tuxfamily.org/non/non.git/
Regards,
\r
On 2011-11-10 11:55, Arno Töll wrote:
> Hi,
> On 10.11.2011 10:01, Björn Esser wrote:
>> jailkit -- here go all the c-binaries
>> jailkit-common -- here go python-scripts, manpages, other no-arch
>
> why? Wouldn't it make slightly more sense to put the manpage where the
> corresponding executa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 10.11.2011 10:01, Björn Esser wrote:
> jailkit -- here go all the c-binaries
> jailkit-common -- here go python-scripts, manpages, other no-arch
why? Wouldn't it make slightly more sense to put the manpage where the
corresponding executable
Hi!
Am 10.11.2011 11:02, schrieb Björn Esser:
>> What version of lintian are you using?
> lintian -V shows me: Lintian v2.4.3+squeeze1
>
> It's the one which is shipped on default with Squeeze.
http://backports-master.debian.org/ has an updated lintian package for
squeeze, please always use that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
lintian -V shows me: Lintian v2.4.3+squeeze1
It's the one which is shipped on default with Squeeze.
Am 10.11.2011 10:58, schrieb Alexander Reichle-Schmehl:
> Hi!
>
> Am 10.11.2011 10:37, schrieb Björn Esser:
>
>>> "Newer" versions of lintian (ar
Hi!
Am 10.11.2011 10:37, schrieb Björn Esser:
>> "Newer" versions of lintian (around 2.5.1 or so) will check direct
>> dependencies (that are built from the same source) if said dependencies
>> are processed together.
[..]
> So what shall I try to get things fixed?
What version of lintian are you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> "Newer" versions of lintian (around 2.5.1 or so) will check direct
> dependencies (that are built from the same source) if said dependencies
> are processed together.
>
> So if you placed your manpage correctly in jailkit-common and jailkit
> dep
On 2011-11-10 10:01, Björn Esser wrote:
> Hi there!
>
Hi,
> I'm just working on packaging. When I build on source into 2 pkgs.
>
> Theese are the two packages:
>
> jailkit -- here go all the c-binaries
> jailkit-common -- here go python-scripts, manpages, other no-arch
>
> After building
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there!
I'm just working on packaging. When I build on source into 2 pkgs.
Theese are the two packages:
jailkit -- here go all the c-binaries
jailkit-common -- here go python-scripts, manpages, other no-arch
After building the pkg, lintian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there!
I'm just working on packaging. When I build on source into 2 pkgs.
Theese are the two packages:
jailkit -- here go all the c-binaries
jailkit-common -- here go python-scripts, manpages, other no-arch
After building the pkg, lintian
On Sun, Dec 12, 2010 at 01:21:20AM +0100, Emmanuel Kasper wrote:
> Hello
> With a couple of other folks following ITP #424905, I am trying to
> get a newer version of MAME, the arcade emulator in debian. We have
> now a working package and I am trying to understand how to properly
> create virtual
Hello
With a couple of other folks following ITP #424905, I am trying to get a
newer version of MAME, the arcade emulator in debian. We have now a
working package and I am trying to understand how to properly create
virtual package since we have to deal with a rename in upstream ( The
Unix Por
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Harry Rickards wrote:
> Sorry to bother everyone again with a noob question (Google was no
> help), but how do you define which files go in which package when you
> have multiple packages for one tarball. I've got 4 packages,
> libw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry to bother everyone again with a noob question (Google was no
help), but how do you define which files go in which package when you
have multiple packages for one tarball. I've got 4 packages,
libweed-dev, libweed0, lives and lives-data.
Nico Golde wrote...
> Did you see http://wiki.debian.org/PkgSplit?
Not until now, and now I'm scared. This is obviously the worst way to do
it. An older article linked from there is
http://lists.debian.org/debian-mentors/2007/04/msg00346.html which
describes my impression and gave the right hint
Hi Christoph,
* Christoph Biedl <[EMAIL PROTECTED]> [2008-10-23 19:52]:
> This topic has been annyoing me for years: I had started a small
> (architecture independent) packages. dh-make created a sound build
> configuration for me and everythings works like a charm. But after a
> while it turns o
This topic has been annyoing me for years: I had started a small
(architecture independent) packages. dh-make created a sound build
configuration for me and everythings works like a charm. But after a
while it turns out I should split the result into several packages,
and every time I look for a
angelog name to dh_installchangelogs). But if
you do specify files to install on the command line, dh_install* will
generally operate on the first package specified.
> 1- why the "dh_install java.ini mono.ini etc/php5/conf.d" line cross rule
> limits when in multiple packages Found
some weird things.
1- why the "dh_install java.ini mono.ini etc/php5/conf.d" line cross rule
limits when in multiple packages
Found that must be one file and one dest per line.
2- unable to find yet documentation about phony rules not having "-" character
in name. Maybe I misu
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, wa
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
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, wa
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
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 th
On Mon, 25 Mar 2002, Ola Lundqvist wrote:
>On Mon, Mar 25, 2002 at 05:02:34PM +0200, Jan Ekholm wrote:
>> On Fri, 22 Mar 2002, Gergely Nagy wrote:
>>
>> >> I know how to make single packages (at least they seem to work), but have
>> >> no idea where to start for a multipackage thing. What documen
On Mon, 25 Mar 2002, Ola Lundqvist wrote:
>On Mon, Mar 25, 2002 at 05:02:34PM +0200, Jan Ekholm wrote:
>> On Fri, 22 Mar 2002, Gergely Nagy wrote:
>>
>> >> I know how to make single packages (at least they seem to work), but have
>> >> no idea where to start for a multipackage thing. What docume
On Mon, Mar 25, 2002 at 05:02:34PM +0200, Jan Ekholm wrote:
> On Fri, 22 Mar 2002, Gergely Nagy wrote:
>
> >> I know how to make single packages (at least they seem to work), but have
> >> no idea where to start for a multipackage thing. What documentation could
> >> I read in order to understand
On Fri, 22 Mar 2002, Gergely Nagy wrote:
>> I know how to make single packages (at least they seem to work), but have
>> no idea where to start for a multipackage thing. What documentation could
>> I read in order to understand the procedure, or what simple existing
>> package could I have a look
On Mon, Mar 25, 2002 at 05:02:34PM +0200, Jan Ekholm wrote:
> On Fri, 22 Mar 2002, Gergely Nagy wrote:
>
> >> I know how to make single packages (at least they seem to work), but have
> >> no idea where to start for a multipackage thing. What documentation could
> >> I read in order to understand
On Fri, 22 Mar 2002, Gergely Nagy wrote:
>> I know how to make single packages (at least they seem to work), but have
>> no idea where to start for a multipackage thing. What documentation could
>> I read in order to understand the procedure, or what simple existing
>> package could I have a look
> I know how to make single packages (at least they seem to work), but have
> no idea where to start for a multipackage thing. What documentation could
> I read in order to understand the procedure, or what simple existing
> package could I have a look at?
>
dh_make can generate rules for multi-b
Hi all,
This is my first post here, so I may be in the entirely wrong forum.
Anyway, I'm packaging a largish game we're making. It's a Python game
written using Pygame, and contains ~20MB of static data, such as graphics,
scenarios and audio. We'd like to package the thing into two or more
packa
> I know how to make single packages (at least they seem to work), but have
> no idea where to start for a multipackage thing. What documentation could
> I read in order to understand the procedure, or what simple existing
> package could I have a look at?
>
dh_make can generate rules for multi-
Hi all,
This is my first post here, so I may be in the entirely wrong forum.
Anyway, I'm packaging a largish game we're making. It's a Python game
written using Pygame, and contains ~20MB of static data, such as graphics,
scenarios and audio. We'd like to package the thing into two or more
pack
In Tue, 21 Aug 2001 14:01:19 +0200 Eduard cum veritate scripsit :
> I guess too, but the foo-i686 would cause Grave-Bugs soon. But there is
> another issue: I considered to create a special optimisation branches
> for specific CPU types using the following concept:
>
> - Packages are recompiled w
In Tue, 21 Aug 2001 14:01:19 +0200 Eduard cum veritate scripsit :
> I guess too, but the foo-i686 would cause Grave-Bugs soon. But there is
> another issue: I considered to create a special optimisation branches
> for specific CPU types using the following concept:
>
> - Packages are recompiled
On Tue, Aug 21, 2001 at 01:38:35PM +0200, Philipp Frauenfelder wrote:
> Hi Eduard
> I guess he wants to build a
> foo
> package and a
> foo-i686
> package as it was done with libc6 some time ago.
Yes, you're right.
> Viral, you need to build the whole package twice but this can be
> done using
On Tue, Aug 21, 2001 at 01:38:35PM +0200, Philipp Frauenfelder wrote:
> Hi Eduard
> I guess he wants to build a
> foo
> package and a
> foo-i686
> package as it was done with libc6 some time ago.
Yes, you're right.
> Viral, you need to build the whole package twice but this can be
> done using
#include
Philipp Frauenfelder wrote on Tue Aug 21, 2001 um 01:38:35PM:
> I guess he wants to build a
> foo
> package and a
> foo-i686
> package as it was done with libc6 some time ago.
I guess too, but the foo-i686 would cause Grave-Bugs soon. But there is
another issue: I considered to create a
Hi Eduard
On Tue, Aug 21, 2001 at 01:07:44PM +0200, Eduard Bloch wrote:
> Viral wrote on Tue Aug 21, 2001 um 02:29:25PM:
>
> > I need to build an i386 version of a package, and also an i686 optimised
> > version for the same package. Is it possible to build both packages from
> > one source, ins
#include
Viral wrote on Tue Aug 21, 2001 um 02:29:25PM:
> I need to build an i386 version of a package, and also an i686 optimised
> version for the same package. Is it possible to build both packages from
> one source, instead of doing it twice in two different directories ?
Please don't do th
#include
Philipp Frauenfelder wrote on Tue Aug 21, 2001 um 01:38:35PM:
> I guess he wants to build a
> foo
> package and a
> foo-i686
> package as it was done with libc6 some time ago.
I guess too, but the foo-i686 would cause Grave-Bugs soon. But there is
another issue: I considered to create
Hi Eduard
On Tue, Aug 21, 2001 at 01:07:44PM +0200, Eduard Bloch wrote:
> Viral wrote on Tue Aug 21, 2001 um 02:29:25PM:
>
> > I need to build an i386 version of a package, and also an i686 optimised
> > version for the same package. Is it possible to build both packages from
> > one source, in
#include
Viral wrote on Tue Aug 21, 2001 um 02:29:25PM:
> I need to build an i386 version of a package, and also an i686 optimised
> version for the same package. Is it possible to build both packages from
> one source, instead of doing it twice in two different directories ?
Please don't do t
Hi,
I need to build an i386 version of a package, and also an i686 optimised
version for the same package. Is it possible to build both packages from
one source, instead of doing it twice in two different directories ?
viral
--
http://www.infofin.com/~gandalf
"Live for today, gone tomorrow, t
Hi,
I need to build an i386 version of a package, and also an i686 optimised
version for the same package. Is it possible to build both packages from
one source, instead of doing it twice in two different directories ?
viral
--
http://www.infofin.com/~gandalf
"Live for today, gone tomorrow,
* Ganesan Rajagopal <[EMAIL PROTECTED]> [20010112 20:56]:
> {short description}. OpenSLP actually needs three packages, openslpd,
> libopenslp0 and libopenslp-dev. Do I need to send separate ITPs for each
> package or can I send in a single ITP for OpenSLP?
Send a single ITP since they are built f
Hi,
I have recently joined the new maintainer program. I intend to package
OpenSLP (http://www.openslp.org), a free implementation of the IETF Service
Location Protocol (BSD style license).
wnpp says I should send a wishlist bug with subject ITP: {package-name} --
{short description}. OpenSLP a
* Ganesan Rajagopal <[EMAIL PROTECTED]> [20010112 20:56]:
> {short description}. OpenSLP actually needs three packages, openslpd,
> libopenslp0 and libopenslp-dev. Do I need to send separate ITPs for each
> package or can I send in a single ITP for OpenSLP?
Send a single ITP since they are built
Hi,
I have recently joined the new maintainer program. I intend to package
OpenSLP (http://www.openslp.org), a free implementation of the IETF Service
Location Protocol (BSD style license).
wnpp says I should send a wishlist bug with subject ITP: {package-name} --
{short description}. OpenSLP
Richard A Nelson wrote:
> I'd like sendmail-doc and libmilter-dev to depend upon the EXACT version
> of sendmail the're built from.
>
> Is there a standard way to obtain the version of the base binary package?
dpkg-source(1):
Source-Version
The source package version (fro
Richard A Nelson wrote:
> I'd like sendmail-doc and libmilter-dev to depend upon the EXACT version
> of sendmail the're built from.
>
> Is there a standard way to obtain the version of the base binary package?
dpkg-source(1):
Source-Version
The source package version (fr
on available on these files( Or
Ramakrishnan> creating multiple packages in general )?
These are the same as docs, files etc. for single binary packages, but
they tell debhelper which are the docs, files etc. for the names pkg
of the two you have.
So lets take "dirs". With one binary
lp me what to put in these files. Is there ant
documantation available on these files( Or creating multiple packages in
general )?
Ramakrishnan M
World Wide Web: http://www.ee.iitm.ernet.in/~ee98m09
--
"A designer knows he has achieved perfection not when there is nothing
left to add, but w
Hamish Moffatt wrote:
>
> On Tue, Jul 27, 1999 at 08:59:34PM -0500, Ardo van Rangelrooij wrote:
> > Source: libsgmls-perl
> > Section: text
> > Priority: optional
> > Maintainer: Ardo van Rangelrooij <[EMAIL PROTECTED]>
> > Standards-Version: 2.5.1.0
>
> > ...
> > dh_gencontrol
> > dpkg-con
On Tue, Jul 27, 1999 at 08:59:34PM -0500, Ardo van Rangelrooij wrote:
> Source: libsgmls-perl
> Section: text
> Priority: optional
> Maintainer: Ardo van Rangelrooij <[EMAIL PROTECTED]>
> Standards-Version: 2.5.1.0
> ...
> dh_gencontrol
> dpkg-control: error: source package has two conflicti
Hi,
I'm trying to split libsgmls-perl (formarly also known as sgmlspm)
into libsgmls-perl and sgmlspl using the following control file
and rules file:
==
Source: libsgmls-perl
Section: text
Priority: optional
Maintainer: Ardo van Ra
On Mon, Jul 26, 1999 at 09:51:51PM -0400, Gopal Narayanan wrote:
> > Well, potato is GLIBC 2.1. You don't really need to support anything else,
> > so only two packages (686-optimised and non-optimised).
> >
> > Note that the gnulibc1 is NOT for libc2.0 as you have above -- it is
> > for libc5. I
On Mon, Jul 26, 1999 at 09:51:51PM -0400, Gopal Narayanan wrote:
> I haven't upgraded to potato either. Is there a machine that is
> running potato that developers could use to test glibc 2.1 related
> packages?
I'm not sure. I thought master would be running potato (since Branden
uses it to build
On Tue, Jul 27, 1999 at 11:25:28AM +1000, Hamish Moffatt wrote:
> On Sun, Jul 25, 1999 at 05:52:42PM -0400, Gopal Narayanan wrote:
> > i386-pc-linux-gnu-gnulibc2.1 : for libc2.1
> > i386-pc-linux-gnulibc1 : for libc2.0
> > i386-pc-linux-gnulibc1-static : static 2.0
>
On Sun, Jul 25, 1999 at 05:52:42PM -0400, Gopal Narayanan wrote:
> i386-pc-linux-gnu-gnulibc2.1 : for libc2.1
> i386-pc-linux-gnulibc1 : for libc2.0
> i386-pc-linux-gnulibc1-static: static 2.0
> i686-pc-linux-gnu-gnulibc2.1 : 686-optimized for 2.1
> i686-pc-linux-gnu
On Sun, Jul 25, 1999 at 10:04:15PM -0500, John Hasler wrote:
> Gopal Narayanan writes:
> > Based on this, it seems to me that I should make 5 separate wrapper
> > packages, and force dependencies accordingly. Am I right?
>
> How about a single package with a postinst that figures out what binary t
Gopal Narayanan writes:
> Based on this, it seems to me that I should make 5 separate wrapper
> packages, and force dependencies accordingly. Am I right?
How about a single package with a postinst that figures out what binary the
user needs and tells him what to get and how to get it? If you are
I am packaging an install wrapper for the [EMAIL PROTECTED] client. It will go
in the contrib/misc section. One of the conditions of the copyright is
that the user has to download the tarball that contains the binaries
directly from the [EMAIL PROTECTED] official webpage
(http://setiathome.ssl.ber
> built. What creates this file, and is there a special way of handling
> it for multiple packages with the same source? Attached is my
> debian/rules.
Okay, there are a couple of problems:
The library can't be called 'libgst', it has to have the soname in the
packa
I just split my package into three, seperating the info documentation
and the library, and I'm having trouble building the .changes file.
At the end of debuild, debian/files represents only the third package
built. What creates this file, and is there a special way of handling
it for mul
91 matches
Mail list logo
