From: Daniel Skarda <0rfelyus@ucw.cz>
Cc: Hamish Moffatt <hamish@cloud.net.au>
Subject: Debian packages for guile-gtk-1.2 CVS
Date: Thu, 12 Feb 2004 21:52:19 +0100 [thread overview]
Message-ID: <m0hdxwkol8.fsf_-_@hobitin.ucw.cz> (raw)
In-Reply-To: <m0k73tmb05.fsf@hobitin.ucw.cz> (Daniel Skarda's message of "Thu, 15 Jan 2004 17:28:58 +0100")
Hello,
I made unofficial Debian packages from guile-gtk-1.2 CVS. I started with
original Hamish's packages from Debian unstable and made following
modifications:
* I renamed the packages to libgtk1.2-guile and libgtk1.2-guile-dev, since
I felt that long package names (like libguilegtkglarea) are very hard to
read and moreover there are already packages with names like libgtk-
perl, libgtk-ruby16 so I guess this is more consistent with Debian
naming conventions (I do not know if exactly these are explicit or not)
* I made new packages for new library bindings to prevent increase
dependencies of libgtk1.2-guile package. Now there is libglade0-guile,
libgdk-pixbuf-guile and gtkglarea-guile.
* The package has version 0.31+cvs20040128
deb http://www.ucw.cz/~0rfelyus/debian .
deb-src http://www.ucw.cz/~0rfelyus/debian .
I have not made many Debian packages in past, in fact I am quite new to
this. So please have mercy when you judge my work. It is possible that I
unintentionally broke some Debian packaging policies or made a mistake.
I would appreciate any help or advice in this area.
0.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next parent reply other threads:[~2004-02-12 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m0y8s9o3et.fsf@hobitin.ucw.cz>
[not found] ` <20040115120833.GA12617@cloud.net.au>
[not found] ` <m0k73tmb05.fsf@hobitin.ucw.cz>
2004-02-12 20:52 ` Daniel Skarda [this message]
2004-02-13 12:42 ` Debian packages for guile-gtk-1.2 CVS rm
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=m0hdxwkol8.fsf_-_@hobitin.ucw.cz \
--to=0rfelyus@ucw.cz \
--cc=hamish@cloud.net.au \
/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).