Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> writes:
> On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
>> > Please give me some hints/suggestions what should be done in such
>> > situation? Are there any packages with that situation in our archive?
>> Since you are the only o
On Sat, Apr 03, 2004 at 11:30:13AM -0600, Steve Langasek wrote:
> > libnetwibab-dev ? what's that suffix ab ?
> > I made libnetwib-dev now.
> It was part of the name of the static lib quoted in your previous email.
> If it's not supposed to be part of the lib name, then yes, amend the
> package nam
On Sat, Apr 03, 2004 at 07:22:13PM +0200, Bartosz Fenski aka fEnIo wrote:
> On Sat, Apr 03, 2004 at 11:14:22AM -0600, Steve Langasek wrote:
> > > Well I thought about it, but this doesn't solve every my doubt.
> > > How could I name this package? Are there any policies about it?
> > > What if next
On Sat, Apr 03, 2004 at 11:14:22AM -0600, Steve Langasek wrote:
> > Well I thought about it, but this doesn't solve every my doubt.
> > How could I name this package? Are there any policies about it?
> > What if next version occures? How to solve it?
>
> > Upstream maintainer answered me, and he t
On Fri, Apr 02, 2004 at 11:07:59PM +0200, Bartosz Fenski aka fEnIo wrote:
> On Fri, Apr 02, 2004 at 10:29:47PM +0200, Andreas Metzler wrote:
> > > I would like to package some very useful set of utilities[1].
> > > It depends on library of the same author[2].
> > > Unfortunatelly SONAME of this lib
Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> writes:
> On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
>> > Please give me some hints/suggestions what should be done in such
>> > situation? Are there any packages with that situation in our archive?
>> Since you are the only o
On Sat, Apr 03, 2004 at 11:30:13AM -0600, Steve Langasek wrote:
> > libnetwibab-dev ? what's that suffix ab ?
> > I made libnetwib-dev now.
> It was part of the name of the static lib quoted in your previous email.
> If it's not supposed to be part of the lib name, then yes, amend the
> package nam
On Sat, Apr 03, 2004 at 07:22:13PM +0200, Bartosz Fenski aka fEnIo wrote:
> On Sat, Apr 03, 2004 at 11:14:22AM -0600, Steve Langasek wrote:
> > > Well I thought about it, but this doesn't solve every my doubt.
> > > How could I name this package? Are there any policies about it?
> > > What if next
On Sat, Apr 03, 2004 at 11:14:22AM -0600, Steve Langasek wrote:
> > Well I thought about it, but this doesn't solve every my doubt.
> > How could I name this package? Are there any policies about it?
> > What if next version occures? How to solve it?
>
> > Upstream maintainer answered me, and he t
On Fri, Apr 02, 2004 at 11:07:59PM +0200, Bartosz Fenski aka fEnIo wrote:
> On Fri, Apr 02, 2004 at 10:29:47PM +0200, Andreas Metzler wrote:
> > > I would like to package some very useful set of utilities[1].
> > > It depends on library of the same author[2].
> > > Unfortunatelly SONAME of this lib
On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
> > Please give me some hints/suggestions what should be done in such
> > situation? Are there any packages with that situation in our archive?
> Since you are the only one using I would say link it in
> static. Problem solved.
I
On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
> > Please give me some hints/suggestions what should be done in such
> > situation? Are there any packages with that situation in our archive?
> Since you are the only one using I would say link it in
> static. Problem solved.
I
On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
> > Please give me some hints/suggestions what should be done in such
> > situation? Are there any packages with that situation in our archive?
> Since you are the only one using I would say link it in
> static. Problem solved.
Y
Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> writes:
> Hello.
>
> I would like to package some very useful set of utilities[1].
> It depends on library of the same author[2].
>
> Unfortunatelly SONAME of this library changes with every new version.
> And to make this problem more annoying, new
On Fri, Apr 02, 2004 at 10:29:47PM +0200, Andreas Metzler wrote:
> > I would like to package some very useful set of utilities[1].
> > It depends on library of the same author[2].
> > Unfortunatelly SONAME of this library changes with every new version.
> > And to make this problem more annoying,
On 2004-04-02 Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> wrote:
> I would like to package some very useful set of utilities[1].
> It depends on library of the same author[2].
> Unfortunatelly SONAME of this library changes with every new version.
> And to make this problem more annoying, new re
On Fri, Apr 02, 2004 at 11:18:11PM +0200, Goswin von Brederlow wrote:
> > Please give me some hints/suggestions what should be done in such
> > situation? Are there any packages with that situation in our archive?
> Since you are the only one using I would say link it in
> static. Problem solved.
Y
Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> writes:
> Hello.
>
> I would like to package some very useful set of utilities[1].
> It depends on library of the same author[2].
>
> Unfortunatelly SONAME of this library changes with every new version.
> And to make this problem more annoying, new
On Fri, Apr 02, 2004 at 10:29:47PM +0200, Andreas Metzler wrote:
> > I would like to package some very useful set of utilities[1].
> > It depends on library of the same author[2].
> > Unfortunatelly SONAME of this library changes with every new version.
> > And to make this problem more annoying,
On 2004-04-02 Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> wrote:
> I would like to package some very useful set of utilities[1].
> It depends on library of the same author[2].
> Unfortunatelly SONAME of this library changes with every new version.
> And to make this problem more annoying, new re
Hello.
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new releases shows very often
(about one version per two weeks).
And no
Hello.
I would like to package some very useful set of utilities[1].
It depends on library of the same author[2].
Unfortunatelly SONAME of this library changes with every new version.
And to make this problem more annoying, new releases shows very often
(about one version per two weeks).
And no
22 matches
Mail list logo
