Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Andrew Clausen
On Mon, Dec 09, 2002 at 12:16:44AM -0500, Daniel Burrows wrote: > So reiserfs has an internal mechanism for reporting whether stuff > is really compatible? Yes. An internal version numbers policy. You call a function (via dlsym) asking if the interface you (i.e. parted) is using, and reiserfs

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Daniel Burrows
On Mon, Dec 09, 2002 at 04:01:29PM +1100, Andrew Clausen <[EMAIL PROTECTED]> was heard to say: > On Mon, Dec 09, 2002 at 02:02:12AM +, Scott James Remnant wrote: > > I don't see why this is a problem, you'd only need to change the > > dlopen() code if there's a SONAME change - and that should

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Andrew Clausen
Hi again, I forgot to mention: what if a backward-compatible API change is made to libreiser? libtool library versioning is designed to deal with all of this... can we use it somehow? Cheers, Andrew

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Andrew Clausen
On Mon, Dec 09, 2002 at 02:02:12AM +, Scott James Remnant wrote: > I don't see why this is a problem, you'd only need to change the > dlopen() code if there's a SONAME change - and that should only change > if there's a binary-incompatible difference. A difference that might > not be picked up

Re: [devel-ref] author/homepage in description

2002-12-08 Thread Adam DiCarlo
"Christopher W. Curtis" <[EMAIL PROTECTED]> writes: > I really don't see much reason for an upstream maintainer, Yes, there's been a lot of good arguments for not bothering with the maintainer name. You can get that from the pkg home page tho... > specifically, but a pointer to a mailing list o

Re: should XML/SGML documentation ship with sources

2002-12-08 Thread Colin Walters
On Sun, 2002-12-08 at 17:32, Adam DiCarlo wrote: > I have a question for further discussion, which I'm unsure about. May > or may not be a policy issue. > > Is it a good practice for SGML or XML documentation to ship with > source? > > Pros: > - providing source lets contributors make patches m

Re: [devel-ref] author/homepage in description

2002-12-08 Thread Adam DiCarlo
Colin Watson <[EMAIL PROTECTED]> writes: > We could just use the existing support for user-defined fields for a > while though. Oh ! Where can I read about these? They aren't mentioned in deb-control(5) or /usr/share/doc/dpkg nor /usr/share/doc/dpkg-dev ... -- ...Adam Di Carlo..<[EMAIL PROTEC

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Scott James Remnant
On Mon, 2002-12-09 at 00:26, Timshel Knoll wrote: > I'm having issues with getting parted's reiserfs support to work in a > way that complies with Debian policy. The issue is that parted dlopen()s > libreiserfs.so and libdal.so (from the libreiserfs-0.3-{0,dev} > packages) for its reiserfs support

Bug#172022: FWD: Re: description writing guide

2002-12-08 Thread Joey Hess
Josip Rodin wrote: > On Fri, Dec 06, 2002 at 12:33:06PM -0500, Joey Hess wrote: > > Package: debian-policy > > > > The dropping of the packaging manual seems increasinly hasty and > > ill-thought-out, when important documentation like this turns out to > > have been dropped from debian in the proc

Bug#172022: FWD: Re: description writing guide

2002-12-08 Thread Joey Hess
Josip Rodin wrote: > How about the attached patch? Looks good to me. -- see shy jo pgp42gc2sLVVN.pgp Description: PGP signature

Re: [devel-ref] author/homepage in description

2002-12-08 Thread Chris Waters
On Sun, Dec 08, 2002 at 05:08:20PM -0600, Adam DiCarlo wrote: > For now, I was planning on recommending something like this: > We recommend that you add the upstream author's name, email address, > and the URL for the package's homepage to the package description in > debian/control. It sh

Re: [devel-ref] author/homepage in description

2002-12-08 Thread Josip Rodin
On Sun, Dec 08, 2002 at 05:08:20PM -0600, Adam DiCarlo wrote: > I'd like to make a "best practices" note in the developers-reference > about how to indicate the upstream author, author's email, and home > page in the package description. I think this is would be a nice > thing. > > Ideally debian

Re: Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Daniel Burrows
On Mon, Dec 09, 2002 at 11:26:14AM +1100, Timshel Knoll <[EMAIL PROTECTED]> was heard to say: > 2. Make parted dlopen() libreiserfs-0.3.so.0 rather than libreiserfs.so. >This will solve the problem, but is not ideal solution since a minor >version upgrade or SONAME change of libreiserfs wi

Putting .so symlinks in libs package for dlopen()ing?

2002-12-08 Thread Timshel Knoll
[Please CC all replies to me] Hi all, I'm having issues with getting parted's reiserfs support to work in a way that complies with Debian policy. The issue is that parted dlopen()s libreiserfs.so and libdal.so (from the libreiserfs-0.3-{0,dev} packages) for its reiserfs support. This is fine, but

Re: [devel-ref] author/homepage in description

2002-12-08 Thread Christopher W. Curtis
On 12/08/02 18:08, Adam DiCarlo wrote: Ideally debian/control's known fields would be extended, e.g., Upstream-Maintainer: John Doe <[EMAIL PROTECTED]> Upstream-Homepage: http://whatever.sourceforge.net/ Is this worthy of filing as a wishlist on dpkg? Personally, there have been many t

Re: [devel-ref] author/homepage in description

2002-12-08 Thread Colin Watson
On Sun, Dec 08, 2002 at 05:24:58PM -0600, Graham Wilson wrote: > On Sun, Dec 08, 2002 at 05:08:20PM -0600, Adam DiCarlo wrote: > > Ideally debian/control's known fields would be extended, e.g., > > > > Upstream-Maintainer: John Doe <[EMAIL PROTECTED]> > > Upstream-Homepage: http://whatever.sou

Re: [devel-ref] author/homepage in description

2002-12-08 Thread Graham Wilson
On Sun, Dec 08, 2002 at 05:08:20PM -0600, Adam DiCarlo wrote: > Ideally debian/control's known fields would be extended, e.g., > > Upstream-Maintainer: John Doe <[EMAIL PROTECTED]> > Upstream-Homepage: http://whatever.sourceforge.net/ > > Is this worthy of filing as a wishlist on dpkg? def

[devel-ref] author/homepage in description

2002-12-08 Thread Adam DiCarlo
I'd like to make a "best practices" note in the developers-reference about how to indicate the upstream author, author's email, and home page in the package description. I think this is would be a nice thing. Ideally debian/control's known fields would be extended, e.g., Upstream-Maintainer:

should XML/SGML documentation ship with sources

2002-12-08 Thread Adam DiCarlo
I have a question for further discussion, which I'm unsure about. May or may not be a policy issue. Is it a good practice for SGML or XML documentation to ship with source? Pros: - providing source lets contributors make patches more easily Cons: - wastes disk space - why bother, just get

Bug#172022: FWD: Re: description writing guide

2002-12-08 Thread Josip Rodin
Hi, How about the attached patch? -- 2. That which causes joy or happiness. Index: policy.sgml === RCS file: /cvs/debian-policy/debian-policy/policy.sgml,v retrieving revision 1.86 diff -u -w -u -r1.86 policy.sgml --- policy.sg

Bug#172022: FWD: Re: description writing guide

2002-12-08 Thread Josip Rodin
On Fri, Dec 06, 2002 at 12:33:06PM -0500, Joey Hess wrote: > Package: debian-policy > > The dropping of the packaging manual seems increasinly hasty and > ill-thought-out, when important documentation like this turns out to > have been dropped from debian in the process. Get your facts straight b

Debian Distribution

2002-12-08 Thread Santo Caruso
Dear Debian, I'm new italian user of your system. I would to distribuite Debian woody to another people but what I find part of your packages with non-free software for ask then autorization for distribution? Sincerly, Santo Caruso --- Santino "skyweb" Caruso Membro CS-LUG (Cosenza Linux User G

Procura-se Profissionais!

2002-12-08 Thread Marcia
Empresa multinacional está contratando interessados com internet, para trabalhar em período parcial ou integral com altos ganhos. Se interessar acesse: www.b2b-venture.cjb.net Marcia Nota: Caso não queira mais receber nossas mensagens, retorne este e-mail com o título: Remover.