From: Daniel Hartwig <mandyke@gmail.com>
To: guile-devel@gnu.org
Subject: Re: About Guile crypto support
Date: Tue, 12 Feb 2013 09:12:28 +0800 [thread overview]
Message-ID: <CAN3veRdQ0K82qFGdaeM3M4p7Gz0mqS+R2QJjBGP183DCWz52BA@mail.gmail.com> (raw)
In-Reply-To: <rmid2w6ub6l.fsf@fnord.ir.bbn.com>
On 11 February 2013 23:23, Greg Troxel <gdt@ir.bbn.com> wrote:
> (First, "all mainstream distros" is only talking about Linux.)
>
> This .so=>devel does not make sense to me. I thought the point was
> that -devel split things that people who wanted to compile against the
> package needed, but not things needed to run. So if a .so is used by a
> program that has been compiled, then it needs to be in the non-devel
> package. I would expect that .so generally belongs in the non-devel
> package, and that the -devel package would have .a and .h.
>
> FWIW, BSD packaging systems do not have this -devel notion
[Assuming a Debian-centric view.]
To be clear, the “.so” files shipped in -dev packages are just
symlinks. The real “.so.X.Y” are shipped in the corresponding library
package, as makes sense.
Nala Ginrut wrote earlier:
> This could be a real issue since almost all mainstream distros packaging
> policy force *.so be put in -devel packages. Though openSUSE/debian adds
> the exception for Guile, I believe it's so hard to do that for every
> packages uses Guile.
What do you mean, “adds the exception for Guile”? The guile-2.0-dev
package contains the same /symlink/ as other -dev packages do. The real
.so is in guile-2.0-libs. I do not see how that is different to any
other library/dev package pair.
next prev parent reply other threads:[~2013-02-12 1:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 12:55 About Guile crypto support Nala Ginrut
2013-02-03 15:37 ` Thien-Thi Nguyen
2013-02-04 1:14 ` Daniel Hartwig
2013-02-04 3:12 ` Nala Ginrut
2013-02-04 3:35 ` Daniel Hartwig
2013-02-04 4:15 ` Nala Ginrut
2013-02-04 23:03 ` Ludovic Courtès
2013-02-05 2:43 ` Nala Ginrut
2013-02-05 2:57 ` Noah Lavine
2013-02-06 13:58 ` Nala Ginrut
2013-02-05 15:48 ` Ludovic Courtès
2013-02-06 4:18 ` Daniel Hartwig
2013-02-06 4:28 ` Daniel Hartwig
2013-02-08 16:21 ` Ludovic Courtès
2013-02-09 1:37 ` Daniel Hartwig
2013-02-09 15:12 ` Ludovic Courtès
2013-02-09 17:02 ` Andy Wingo
2013-02-09 17:50 ` Mark H Weaver
2013-02-09 20:44 ` Noah Lavine
2013-02-09 21:53 ` Ludovic Courtès
2013-02-11 8:20 ` Andy Wingo
2013-02-11 9:15 ` Thien-Thi Nguyen
2013-02-11 10:46 ` Mike Gran
2013-02-11 13:14 ` Ludovic Courtès
2013-02-11 9:51 ` Nala Ginrut
2013-02-11 15:23 ` Greg Troxel
2013-02-12 1:12 ` Daniel Hartwig [this message]
2013-02-12 4:20 ` Nala Ginrut
2013-02-12 5:21 ` Daniel Hartwig
2013-02-12 7:40 ` Dynamic FFI vs Static FFI (was Re: About Guile crypto support) Mark H Weaver
2013-02-12 13:52 ` Ludovic Courtès
2013-02-12 18:24 ` Mark H Weaver
2013-02-12 21:49 ` Ludovic Courtès
2013-02-14 7:21 ` William ML Leslie
2013-02-15 13:34 ` Nala Ginrut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN3veRdQ0K82qFGdaeM3M4p7Gz0mqS+R2QJjBGP183DCWz52BA@mail.gmail.com \
--to=mandyke@gmail.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).