Scripsit Joachim Reichel <[EMAIL PROTECTED]>
> Uups, I missed that I might have to change the name of the library
> itself. Or is it possible to have a package named "libcore++1"
> containing libraries "libcore.so.1"? (If yes, there is still the
> problem that a quite generic (file)name is used.)
Hi,
>>If the names above are still too generic, I think I will use libcore++ as
>>prefix. Or has anyone else another suggestion?
>
> Why not libexact?
Maybe, but I'd prefer if "core" is part of the package name, because is is
known under this name in the scientific community.
>>I'm a bit uncertai
On Tue, Oct 05, 2004 at 06:58:07PM +0200, Joachim Reichel wrote:
>
> If the names above are still too generic, I think I will use libcore++ as
> prefix. Or has anyone else another suggestion?
>
Why not libexact?
> I'm a bit uncertain about potential consequences if the Debian package name
> d
Hi,
Package: wnpp
Severity: wishlist
* Package name: core
This seems a tad generic, especially since it's a library. Maybe
libcoremath or libcore++?
Hmm, you're right. Does your comment only apply to the source package name
or also to the binary package names? I intend to make the following p
On Tue, 2004-10-05 at 09:39 +1000, Rob Weir wrote:
> On Mon, Oct 04, 2004 at 08:51:01PM +0200, Joachim Reichel said
> > Package: wnpp
> > Severity: wishlist
> >
> > * Package name: core
>
> This seems a tad generic, especially since it's a library. Maybe
> libcoremath or libcore++?
Besides,
On Mon, Oct 04, 2004 at 08:51:01PM +0200, Joachim Reichel said
> Package: wnpp
> Severity: wishlist
>
> * Package name: core
This seems a tad generic, especially since it's a library. Maybe
libcoremath or libcore++?
-rob
--
Words of the day:NATO freedom supercomputer AVN diwn MD2 AMEM
6 matches
Mail list logo
