]> jfr.im git - irc.git/blob - software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2002/003274.html
RELEASE -> !RELEASE
[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2002 / 003274.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> [IRCServices] Official Debian Packaging
5 </TITLE>
6 <LINK REL="Index" HREF="index.html" >
7 <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Official%20Debian%20Packaging&In-Reply-To=20021109120940.GA3304%40executor.imperialnet.mig">
8 <META NAME="robots" CONTENT="index,nofollow">
9 <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
10 <LINK REL="Previous" HREF="003273.html">
11 <LINK REL="Next" HREF="003277.html">
12 </HEAD>
13 <BODY BGCOLOR="#ffffff">
14 <H1>[IRCServices] Official Debian Packaging</H1>
15 <B>Andrew Church</B>
16 <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Official%20Debian%20Packaging&In-Reply-To=20021109120940.GA3304%40executor.imperialnet.mig"
17 TITLE="[IRCServices] Official Debian Packaging">achurch at achurch.org
18 </A><BR>
19 <I>Sun Nov 10 04:05:02 PST 2002</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="003273.html">[IRCServices] Official Debian Packaging
22 </A></li>
23 <LI>Next message: <A HREF="003277.html">[IRCServices] Any idea about log files?
24 </A></li>
25 <LI> <B>Messages sorted by:</B>
26 <a href="date.html#3274">[ date ]</a>
27 <a href="thread.html#3274">[ thread ]</a>
28 <a href="subject.html#3274">[ subject ]</a>
29 <a href="author.html#3274">[ author ]</a>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
34 <PRE> Thanks for your message. To take your points in reverse order: the
35 binary data files used by Services are endian-independent, so they should
36 be able to go into /var/share. (I haven't actually tested this, but I
37 don't use fwrite() anywhere except when writing strings, so there shouldn't
38 be any problems. If there are, it's a bug. ;) )
39
40 Services currently assumes all the data files are under a single
41 directory tree, and it'll take a bit of work to redo that; I'll look into
42 it, but I can't promise getting it done soon. As a cheap hack, something
43 like the following (untested) should work, though it leaves a few symlinks
44 hanging around in /var/share/ircservices:
45
46 ./configure -bindest /usr/bin -datdest /var/share/ircservices
47 make install
48 mkdir -p /usr/lib/ircservices
49 rm -rf /usr/lib/ircservices/modules
50 cp -a /var/share/ircservices/modules /usr/lib/ircservices/
51 rm -rf /var/share/ircservices/modules
52 ln -s /usr/lib/ircservices/modules /var/share/ircservices/
53 mkdir -p /usr/share/ircservices
54 rm -rf /usr/share/ircservices/languages
55 cp -a /var/share/ircservices/languages /usr/share/ircservices/
56 rm -rf /var/share/ircservices/languages
57 ln -s /usr/share/ircservices/languages /var/share/ircservices/
58 mkdir -p /var/log/ircservices
59 ln -fs /var/log/ircservices/ircservices.log /var/share/ircservices/
60 mkdir -p /etc/ircservices
61 mv -f /var/share/ircservices/example-*.conf /etc/ircservices/
62 ln -fs /etc/ircservices/{ircservices,modules}.conf /var/share/ircservices/
63
64 --Andrew Church
65 <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org</A>
66 <A HREF="http://achurch.org/">http://achurch.org/</A>
67
68 &gt;<i>Hi,
69 </I>&gt;<i>
70 </I>&gt;<i>I'm writing to this list because I plan to make an official Debian version of
71 </I>&gt;<i>ircservices. I know there is a .deb on the website, but I think it's worth
72 </I>&gt;<i>to put it in the main debian archive, to have it available on each architecture
73 </I>&gt;<i>debian supports, and directly from the package managing system.
74 </I>&gt;<i>
75 </I>&gt;<i>In order to do so, I must plan to do some changes, at least in the directory
76 </I>&gt;<i>structure ircservices use. The main thing I must do to have it included
77 </I>&gt;<i>is to have a more separated directory structure, which refects the FHS.
78 </I>&gt;<i>I'm wondering if this changes can be received upstream, as additional options
79 </I>&gt;<i>to configure and make, without changing the actual default behaviour, but
80 </I>&gt;<i>simply allowing it to be changed calling configure and make with some options.
81 </I>&gt;<i>
82 </I>&gt;<i>In this way there will be no problem for the actual users, who won't see the
83 </I>&gt;<i>changes from their point of view, but the scripts could be used without changes
84 </I>&gt;<i>by the debian maintainer scripts (and thus autobuilders).
85 </I>&gt;<i>
86 </I>&gt;<i>Here are the directory structure I plan to use in the debian version:
87 </I>&gt;<i>
88 </I>&gt;<i>binaries: /usr/bin/
89 </I>&gt;<i>modules: /usr/lib/ircservices/
90 </I>&gt;<i>databases: /var/lib/ircservices/
91 </I>&gt;<i>logs: /var/log/ircservices/
92 </I>&gt;<i>configuration: /etc/ircservices/
93 </I>&gt;<i>
94 </I>&gt;<i>
95 </I>&gt;<i>I hope this (the package and the changes) isn't a problem for you.
96 </I>&gt;<i>Otherwise I'll be happy to talk about it, and eventually withdraw my
97 </I>&gt;<i>proposal.
98 </I>&gt;<i>
99 </I>&gt;<i>BTW I shall ask for an advice: the services database binary format is
100 </I>&gt;<i>architecture dependent or independent?
101 </I>&gt;<i>For example can one simply copy the databases from a little endian to a
102 </I>&gt;<i>big endian machine and expect them to work? In this case I think I'll move
103 </I>&gt;<i>them to /var/share/ircservices insteas of /var/lib/
104 </I>&gt;<i>
105 </I>&gt;<i>Thank in advance,
106 </I>&gt;<i>
107 </I>&gt;<i>--
108 </I>&gt;<i>Guido Trotter - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ultrotter at debian.org</A>
109 </I>
110 </PRE>
111
112 <!--endarticle-->
113 <HR>
114 <P><UL>
115 <!--threads-->
116 <LI>Previous message: <A HREF="003273.html">[IRCServices] Official Debian Packaging
117 </A></li>
118 <LI>Next message: <A HREF="003277.html">[IRCServices] Any idea about log files?
119 </A></li>
120 <LI> <B>Messages sorted by:</B>
121 <a href="date.html#3274">[ date ]</a>
122 <a href="thread.html#3274">[ thread ]</a>
123 <a href="subject.html#3274">[ subject ]</a>
124 <a href="author.html#3274">[ author ]</a>
125 </LI>
126 </UL>
127
128 </body></html>