nging how dpkg-shlibdeps works though.
Perhaps not. Most situations could probably be handled by simply
moving the .shlibs files from the run-time packages to the -dev
packages.
David
--
David Engel
[EMAIL PROTECTED]
o and aim at a merger with glibc (I thought
> this was already attempted in the past, seems my memory is at fault).
ld-linux.so.* was chosen so it would not conflict with other systems.
This makes it easier setup emulations of other systems on Linux and
vice versa. It's not worth changing.
David
--
David Engel
[EMAIL PROTECTED]
- it's called "gcc -I".
David
--
David Engel
[EMAIL PROTECTED]
ld situation. The
dependencies and conflicts are setup to prevent nonsensical
installations such as tcl7.6-dev with tk8.0-dev or tcl8.0-dev with
tk4.2-dev.
David
--
David Engel
[EMAIL PROTECTED]
#x27;t be possible. The only thing
that wouldn't easily be possible is to have multiple development
environments installed in the default location. If you needed
multiple development emvironments, then and only then, would special
treatment be needed. Since we already do this for libc5 and libc6, it
shouldb't be a big deal.
David
--
David Engel
[EMAIL PROTECTED]
which would put it under /usr/X11R6. If
a package uses autoconf, use --prefix=/usr when running configure
which would put it under /usr.
David
--
David Engel
[EMAIL PROTECTED]
a symlink to it named changelog.gz to
comply with Debian policy.
David
--
David EngelODS Networks
[EMAIL PROTECTED] 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
(I
know it still is to me). If such sample scripts were available, I
think it would be a tremendous help to new developers as well as
experienced developers.
David
--
David EngelODS Networks
[EMAIL PROTECTED] 1001 E. Arapaho Road
(972) 234-6400
On Sat, Mar 28, 1998 at 12:12:48AM -0500, Adam P. Harris wrote:
> [You ("David Engel")]
> >This is correct -- you must run ldconfig. If the new libraries are
> >installed into /lib or /usr/lib, you can get away with not running
> >ldconfig but you should still r
sr/lib, you can get away with not running
ldconfig but you should still run it anyway to get the entries into
/etc/ld.so.cache.
David
--
David EngelODS Networks
[EMAIL PROTECTED] 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
do still need to call ldconfig in postinst in
> > order to update /etc/ld.so.cache.
>
> I belive that is correct. David Engel can tell us for sure.
This is correct.
> > Is this the issue? It would be a pretty simple addition to Ch 12 of the
> > Packaging Manual.
>
ncies like on libc6, etc...)
>
> After some discussions a few months ago on debian-devel (or -policy),
> some people (I remember David Engel and myself) argued that for some
> packages you might also want:
> libfoo depends on libfoog
Yes.
> libfoo-altdev depends on libfo
12 matches
Mail list logo
