xlibs (4.1.0-16) depends on xlibs ( 4.1.0) and on other packages.
Assuming this is not an error, how can it be and what does it achieve?
--
Shaul Karl
email: shaulka(replace with the at - @ - character)bezeqint.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Mon, May 06, 2002 at 04:53:29PM +0300, [EMAIL PROTECTED] wrote:
xlibs (4.1.0-16) depends on xlibs ( 4.1.0) and on other packages.
Assuming this is not an error, how can it be and what does it achieve?
It looks like it is probably an automatically generated dependency detected
by
[EMAIL PROTECTED] immo vero scripsit:
xlibs (4.1.0-16) depends on xlibs ( 4.1.0) and on other packages.
Assuming this is not an error, how can it be and what does it achieve?
xlibs contains libraries that depend on other libraries which
happen to be in xlibs package also.
I do not recommend
hi
someone was suggesting to not provide shared libraries;
unfortunately this may create problems in the HPPA architecture:
indeed, it is not legal there to link portable (-fPIC) code with non
portable (afair); so , if someone else wants to build a shared
library that uses your library, then
hi
I would like to try to build some packages on other architectures
than i386; I have seen the list of debian machines, and I have logged
in on lully, and I have tried to use
$ sbuild mypackage
but it fails (seems that I am not allowed to use sudo),
so I can't install the necessary
On Mon, May 06, 2002 at 05:50:52PM +0200, Andrea Mennucc wrote:
hi
I would like to try to build some packages on other architectures
than i386; I have seen the list of debian machines, and I have logged
in on lully, and I have tried to use
$ sbuild mypackage
but it fails (seems
Hello,
I'd like to become a Debian package maintainer and I have found a
package that interests me a lot but that isn't in Debian yet. It is
KVIrc 3, the next version of the KVIrc IRC client which is as 2.1 in
Debian already.
I have mailed Robin Verduijn (current KVIrc 2 maintainer) and Szymon
Hi Till,
On Mon, May 06, 2002 at 10:13:59PM +0200, Till Gerken wrote:
Hello,
I'd like to become a Debian package maintainer and I have found a
package that interests me a lot but that isn't in Debian yet. It is
KVIrc 3, the next version of the KVIrc IRC client which is as 2.1 in
Debian
On Mon, May 06, 2002 at 11:18:38AM -0400, Matt Zimmerman wrote:
On Mon, May 06, 2002 at 04:53:29PM +0300, [EMAIL PROTECTED] wrote:
xlibs (4.1.0-16) depends on xlibs ( 4.1.0) and on other packages.
Assuming this is not an error, how can it be and what does it achieve?
It looks like it is
Roger Leigh [EMAIL PROTECTED] writes:
The last three all use custom m4 macrocode I wrote (available in the
ac-archive, renamed and specialised for use in ijs). Due to the
unstable nature of the source, I defaulted to -release versioning, and
disabling shared libraries by default, but the
On Mon, 06 May 2002, Roger Leigh wrote:
Is it common or good practice to keep the build for Debian separate
for upstream, or should I really get my changes incorporated upstream
first? It's just that I don't really see this happening all that soon
(it at all).
Go ahead and fork it, as long
Roger Leigh [EMAIL PROTECTED] immo vero scripsit:
Would the following scheme be acceptable to you?:
Package: libijs-0.34
contains libijs-0.34.so
In my little testing, if I build a library with
-export-dynamic -version-info 0:0:0 -release 1.0.1
I get:
$ ls -1 .libs/
Hi,
Have you read /usr/share/doc/kernel-package/README.modules? It
states that:
==
make-kpkg arranges to cd into each modules top directory,
/usr/src/modules/mod-name/, and runs ./debian/rules target.
13 matches
Mail list logo
