unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bo Forslund <bo.forslund@abc.se>
Subject: some rpm building questions
Date: 04 Oct 2002 00:06:04 +0200	[thread overview]
Message-ID: <1033682765.2197.59.camel@li.mine.nu> (raw)



Hello!

I have some questions about how to pack a guile rpm.


Would rpm packaging like this be good? Or should all .h files go to a
-devel package?


guile
	/usr/bin/*

libguile
	/usr/lib/libguile/*

libguile-devel
	/usr/include/libguile.h
	/usr/include/libguile/*

guile-lib
	/usr/share/aclocal/guile.m4 
	/usr/share/doc/*
	/usr/share/guile/1.6.0/ice-9/*
	/usr/include/guile/gh.h
	(/usr/share/guile/1.6.0/scripts/*)    ???

guile-oop
	/usr/share/guile/1.6.0/oop/*

guile-srfi
	/usr/share/guile/1.6.0/srfi/*
	/usr/lib/libguile-srfi-*


guile-readline
	/usr/include/guile-readline/readline.h 
	/usr/lib/libguilereadline-v-12.*
	
guile-ltdl
	conflicting libltdl here already

I don't know where to put /usr/share/guile/1.6.0/scripts/*. Should it go
to it's own package or to the guile or guile-lib package?

And then libltdl. As there already is one installed, can it just be
omitted or shall it go to a package? But then, how can it be installed
if there is a conflicting one installed already.

Well.. this is the rpm spec so far.

And curiously,  What does ice-9 stand for.

Bo



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2002-10-03 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 22:06 Bo Forslund [this message]
2002-10-04  2:20 ` some rpm building questions Bo Forslund
2002-10-04 11:56   ` Han-Wen Nienhuys
2002-10-04 12:30   ` Marius Vollmer
2002-10-04 13:08     ` rm
2002-10-04 15:48       ` Rob Browning
2002-10-08 21:27       ` Marius Vollmer
2002-10-04 16:04 ` Rob Browning

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=1033682765.2197.59.camel@li.mine.nu \
    --to=bo.forslund@abc.se \
    /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).