On Wednesday 07 January 2004 05:20, Chris Cheney wrote:
> On Tue, Jan 06, 2004 at 12:00:19PM +0100, Jean-Michel Kelbert wrote:
> > To my mind it is not a good idea to include lib in a binary package, so
> > I don't want to do only one package.
>
> To be honest I don't know why most of the kde prog
On Tue, Jan 06, 2004 at 12:00:19PM +0100, Jean-Michel Kelbert wrote:
> To my mind it is not a good idea to include lib in a binary package, so
> I don't want to do only one package.
To be honest I don't know why most of the kde programs have libraries at
all. Except for the ones that have kparts o
On Tue, 6 Jan 2004, Jean-Michel Kelbert wrote:
> Le 06/01/04 à 13:32 Tomas Pospisek's Mailing Lists ([EMAIL PROTECTED])
> écrivait :
> > Having a lib only makes sense when and if there are other packages using
> > it. Are there any? Basing your decision on the _doctrine_ that libs should
> > be p
> it is not a good idea to include lib in a binary package
Why?
This is true if library is useful for other application development.
Isn't k3b library useful for k3b only?
Le 06/01/04 à 13:32 Tomas Pospisek's Mailing Lists ([EMAIL PROTECTED]) écrivait
:
> Having a lib only makes sense when and if there are other packages using
> it. Are there any? Basing your decision on the _doctrine_ that libs should
> be packaged separately isn't a very good idea: the same doctri
On Tue, 6 Jan 2004, Jean-Michel Kelbert wrote:
> Then we'll have :
>
> k3b
> k3blibs
> k3blibs-deb
>
> To my mind it is not a good idea to include lib in a binary package, so
> I don't want to do only one package.
>
> Comments are welcome
Having a lib only makes sense when and if there are other
Le 06/01/04 à 11:09 Chris Cheney ([EMAIL PROTECTED]) écrivait :
> Yes, I'm actually surprised that the ftp admin team let it through. They
> have rejected similiar things in the past. To be honest it looks like
> their _NEW_ processing isn't happening right now and things are being
> immediately ac
On Tue, Jan 06, 2004 at 11:01:14AM +0300, Nikita V. Youshchenko wrote:
> > Hi,
> >
> > I am the maintenair of k3b.
>
> Could you please explain what's the rationale of splitting k3b in several
> packages? Seems that k3b libraries are used only by k3b itself, and none of
> the k3b packages is arch
> Hi,
>
> I am the maintenair of k3b.
Could you please explain what's the rationale of splitting k3b in several
packages? Seems that k3b libraries are used only by k3b itself, and none of
the k3b packages is architecture-independent. Isn't it better to put
everything in a single package?
Hi,
I am the maintenair of k3b. I recognize that this problem is due to a
packaging problem. This night version 0.10.3-4 will enter into sid. It
purpuses is to solve the k3bsetup problem.
Tomorrow, I will create a new package which will solve this problem.
Sorry for the annoyance.
But please
10 matches
Mail list logo
