On Mon, Apr 30, 2001 at 01:37:52AM +0100, James Troup wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > (1) It could be documented on http://keyring.debian.org/
>
> I'm sure it could...[0]
And I would do it if I had the faintest clue what I was talking
about. But as I don't, please could
Hello!
I'm trying to package a library, but I have some questions regarding
the name the package should have.
First of all, the policy says that the library package must something
like libpackagesoname, so if the library that the package has looks
like:
lrwxrwxrwx1 jose jose
James Troup wrote:
> The canonical source for the debian keyring _is_[2] kerying.debian.org
> (via anon-rsync); period. The package is a convenience, nothing
> more[3].
A package which is horribly outdated is everything but a "convenience".
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> but, what happens with the old package (libgpgme0) and with the programs
> c
El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
[...]
> Nothing happens to the old package.
>
> When a new shared library comes out that is incompatible with an old
> shared library, both libraries should be installed, this is why the
> soname is in the package name. It allows simult
On Mon, 30 Apr 2001, Santiago Vila wrote:
> James Troup wrote:
> > The canonical source for the debian keyring _is_[2] kerying.debian.org
> > (via anon-rsync); period. The package is a convenience, nothing
> > more[3].
>
> A package which is horribly outdated is everything but a "convenience".
T
I just noticed the debian/rules file for mirrormagic which I inherited from
Joey Hess uses dh_testroot to check that the build is run as root (or
fakeroot).
I'm wondering what the justification for doing this is. It prevents, for
instance, a home user compiling his own deb before installing unle
Jose Carlos Garcia Sogo <[EMAIL PROTECTED]> writes:
JCGS> I'm trying to package a library, but I have some questions regarding
JCGS> the name the package should have.
JCGS>
JCGS> First of all, the policy says that the library package must something
JCGS> like libpackagesoname, so if the library
On Mon, Apr 30, 2001 at 01:22:03PM +0200, Jose Carlos Garcia Sogo wrote:
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> but
On Mon, Apr 30, 2001 at 11:50:37PM +1000, Drew Parsons wrote:
> I just noticed the debian/rules file for mirrormagic which I inherited from
> Joey Hess uses dh_testroot to check that the build is run as root (or
> fakeroot).
>
> I'm wondering what the justification for doing this is. It prevents
> Yes, but now I have another question. The library itself has a
> different version numbering.
That's ok. Version number and SO name are not the same and need not
have any correlation. Many different versions can have the same soname
and that's ok.
> In this way, current version is 0.2.1, but
On 30 Apr 2001, Jose Carlos Garcia Sogo wrote:
> El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
> [...]
> > Nothing happens to the old package.
> > When a new shared library comes out that is incompatible with an old
> > shared library, both libraries should be installed, this is why
On Mon, 30 Apr 2001, Henrique M Holschuh wrote:
> On Mon, 30 Apr 2001, Santiago Vila wrote:
> > James Troup wrote:
> > > The canonical source for the debian keyring _is_[2] kerying.debian.org
> > > (via anon-rsync); period. The package is a convenience, nothing
> > > more[3].
> > A package which
On Mon, Apr 30, 2001 at 11:50:37PM +1000, Drew Parsons wrote:
> I'm wondering what the justification for doing this is. It prevents, for
> instance, a home user compiling his own deb before installing unless he
> specifically compiles it under root or fakeroot.
The build process needs to produce
You might want to refer to the libtool-doc package: 'info libtool' and go
to the Menu node on Versioning. That is the source of the message you
quoted and it contains more information as well.
On Mon, Apr 30, 2001 at 10:35:12AM -0400, [EMAIL PROTECTED] wrote:
> > Yes, but now I have another ques
On 30 Apr 2001, James Troup wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > (1) It could be documented on http://keyring.debian.org/
>
> I'm sure it could...[0]
Is the procedure for useing anon-rsync documented somewhere else?
> The canonical source for the debian keyring _is_[2] keryi
"Steve M. Robbins" <[EMAIL PROTECTED]> writes:
> On Thu, Apr 26, 2001 at 04:07:38PM -0400, Wolfgang Sourdeau wrote:
>
> > The dh_installchangelogs doesn't accept a ChangeLog parameter when the
> > package is a native debian package. However, the GNU HaliFAX project
> > is (as its name implies) an
Drew Parsons <[EMAIL PROTECTED]> writes:
> I just noticed the debian/rules file for mirrormagic which I inherited from
> Joey Hess uses dh_testroot to check that the build is run as root (or
> fakeroot).
There are two parts to building a Debian package:
(a) compiling/linking/etc. the application
On Mon, Apr 30, 2001 at 10:39:13PM +0200, Robert Bihlmeyer wrote:
> "Steve M. Robbins" <[EMAIL PROTECTED]> writes:
>
> > On Thu, Apr 26, 2001 at 04:07:38PM -0400, Wolfgang Sourdeau wrote:
> >
> > > The dh_installchangelogs doesn't accept a ChangeLog parameter when the
> > > package is a native de
On Mon, Apr 30, 2001 at 01:37:16PM -0800, Britton wrote:
>
> On 30 Apr 2001, James Troup wrote:
>
> > Julian Gilbey <[EMAIL PROTECTED]> writes:
> >
> > > (1) It could be documented on http://keyring.debian.org/
> >
> > I'm sure it could...[0]
It didn't take me too long (just now) to work out tha
* Britton
| On 30 Apr 2001, James Troup wrote:
|
| > Julian Gilbey <[EMAIL PROTECTED]> writes:
| >
| > > (1) It could be documented on http://keyring.debian.org/
| >
| > I'm sure it could...[0]
|
| Is the procedure for useing anon-rsync documented somewhere else?
rsync keyring.debian.org::keyr
> > I think the answer is simply that you shouldn't be treating this
> > as a "debian native" package.
>
> Why not? If no changes take place from upstream version to debian
> source, tagging on "-1", and creating an empty Debianization diff is
> unsound.
There's nothing wrong with an empty diff.
On Mon, Apr 30, 2001 at 01:37:52AM +0100, James Troup wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > (1) It could be documented on http://keyring.debian.org/
>
> I'm sure it could...[0]
And I would do it if I had the faintest clue what I was talking
about. But as I don't, please coul
Hello!
I'm trying to package a library, but I have some questions regarding
the name the package should have.
First of all, the policy says that the library package must something
like libpackagesoname, so if the library that the package has looks
like:
lrwxrwxrwx1 jose jose
James Troup wrote:
> The canonical source for the debian keyring _is_[2] kerying.debian.org
> (via anon-rsync); period. The package is a convenience, nothing
> more[3].
A package which is horribly outdated is everything but a "convenience".
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> but, what happens with the old package (libgpgme0) and with the programs
>
El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
[...]
> Nothing happens to the old package.
>
> When a new shared library comes out that is incompatible with an old
> shared library, both libraries should be installed, this is why the
> soname is in the package name. It allows simul
On Mon, 30 Apr 2001, Santiago Vila wrote:
> James Troup wrote:
> > The canonical source for the debian keyring _is_[2] kerying.debian.org
> > (via anon-rsync); period. The package is a convenience, nothing
> > more[3].
>
> A package which is horribly outdated is everything but a "convenience".
I just noticed the debian/rules file for mirrormagic which I inherited from
Joey Hess uses dh_testroot to check that the build is run as root (or
fakeroot).
I'm wondering what the justification for doing this is. It prevents, for
instance, a home user compiling his own deb before installing unl
Jose Carlos Garcia Sogo <[EMAIL PROTECTED]> writes:
JCGS> I'm trying to package a library, but I have some questions regarding
JCGS> the name the package should have.
JCGS>
JCGS> First of all, the policy says that the library package must something
JCGS> like libpackagesoname, so if the library
On Mon, Apr 30, 2001 at 01:22:03PM +0200, Jose Carlos Garcia Sogo wrote:
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> bu
On Mon, Apr 30, 2001 at 11:50:37PM +1000, Drew Parsons wrote:
> I just noticed the debian/rules file for mirrormagic which I inherited from
> Joey Hess uses dh_testroot to check that the build is run as root (or
> fakeroot).
>
> I'm wondering what the justification for doing this is. It prevent
> Yes, but now I have another question. The library itself has a
> different version numbering.
That's ok. Version number and SO name are not the same and need not
have any correlation. Many different versions can have the same soname
and that's ok.
> In this way, current version is 0.2.1, bu
On 30 Apr 2001, Jose Carlos Garcia Sogo wrote:
> El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
> [...]
> > Nothing happens to the old package.
> > When a new shared library comes out that is incompatible with an old
> > shared library, both libraries should be installed, this is why
On Mon, 30 Apr 2001, Henrique M Holschuh wrote:
> On Mon, 30 Apr 2001, Santiago Vila wrote:
> > James Troup wrote:
> > > The canonical source for the debian keyring _is_[2] kerying.debian.org
> > > (via anon-rsync); period. The package is a convenience, nothing
> > > more[3].
> > A package whic
On Mon, Apr 30, 2001 at 11:50:37PM +1000, Drew Parsons wrote:
> I'm wondering what the justification for doing this is. It prevents, for
> instance, a home user compiling his own deb before installing unless he
> specifically compiles it under root or fakeroot.
The build process needs to produc
You might want to refer to the libtool-doc package: 'info libtool' and go
to the Menu node on Versioning. That is the source of the message you
quoted and it contains more information as well.
On Mon, Apr 30, 2001 at 10:35:12AM -0400, [EMAIL PROTECTED] wrote:
> > Yes, but now I have another que
On 30 Apr 2001, James Troup wrote:
> Julian Gilbey <[EMAIL PROTECTED]> writes:
>
> > (1) It could be documented on http://keyring.debian.org/
>
> I'm sure it could...[0]
Is the procedure for useing anon-rsync documented somewhere else?
> The canonical source for the debian keyring _is_[2] kery
"Steve M. Robbins" <[EMAIL PROTECTED]> writes:
> On Thu, Apr 26, 2001 at 04:07:38PM -0400, Wolfgang Sourdeau wrote:
>
> > The dh_installchangelogs doesn't accept a ChangeLog parameter when the
> > package is a native debian package. However, the GNU HaliFAX project
> > is (as its name implies) a
Drew Parsons <[EMAIL PROTECTED]> writes:
> I just noticed the debian/rules file for mirrormagic which I inherited from
> Joey Hess uses dh_testroot to check that the build is run as root (or
> fakeroot).
There are two parts to building a Debian package:
(a) compiling/linking/etc. the applicatio
On Mon, Apr 30, 2001 at 10:39:13PM +0200, Robert Bihlmeyer wrote:
> "Steve M. Robbins" <[EMAIL PROTECTED]> writes:
>
> > On Thu, Apr 26, 2001 at 04:07:38PM -0400, Wolfgang Sourdeau wrote:
> >
> > > The dh_installchangelogs doesn't accept a ChangeLog parameter when the
> > > package is a native d
On Mon, Apr 30, 2001 at 01:37:16PM -0800, Britton wrote:
>
> On 30 Apr 2001, James Troup wrote:
>
> > Julian Gilbey <[EMAIL PROTECTED]> writes:
> >
> > > (1) It could be documented on http://keyring.debian.org/
> >
> > I'm sure it could...[0]
It didn't take me too long (just now) to work out th
* Britton
| On 30 Apr 2001, James Troup wrote:
|
| > Julian Gilbey <[EMAIL PROTECTED]> writes:
| >
| > > (1) It could be documented on http://keyring.debian.org/
| >
| > I'm sure it could...[0]
|
| Is the procedure for useing anon-rsync documented somewhere else?
rsync keyring.debian.org::key
> > I think the answer is simply that you shouldn't be treating this
> > as a "debian native" package.
>
> Why not? If no changes take place from upstream version to debian
> source, tagging on "-1", and creating an empty Debianization diff is
> unsound.
There's nothing wrong with an empty diff.
44 matches
Mail list logo