software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2007/003303.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] Build prefix/FHS compliance
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Build%20prefix/FHS%20compliance&In-Reply-To=1184321919.6368.14.camel%40regulus.retout.co.uk">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="003302.html">
  11    <LINK REL="Next"  HREF="003304.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Build prefix/FHS compliance</H1>
  15     <B>Andrew Church</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Build%20prefix/FHS%20compliance&In-Reply-To=1184321919.6368.14.camel%40regulus.retout.co.uk"
  17        TITLE="[IRCServices Coding] Build prefix/FHS compliance">achurch at achurch.org
  18        </A><BR>
  19     <I>Fri Jul 13 19:54:25 PDT 2007</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003302.html">[IRCServices Coding] Build prefix/FHS compliance
  22 </A></li>
  23         <LI>Next message: <A HREF="003304.html">[IRCServices Coding] Build prefix/FHS compliance
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#3303">[ date ]</a>
  27               <a href="thread.html#3303">[ thread ]</a>
  28               <a href="subject.html#3303">[ subject ]</a>
  29               <a href="author.html#3303">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>     Thanks for the notes.  I'm swamped with work at the moment, but I'll
  35 definitely look into addressing the first two points for the next beta
  36 release.
  37
  38      As far as FHS compliance goes, can you make any specific suggestions?
  39 I'm not sure how much I can do, since Services' design requires all data
  40 under a common hierarchy, and at this point it's a bit late to go back and
  41 change that so it works reliably with scattered files.  It may suffice in
  42 at least some cases to use absolute rather than relative paths, though, so
  43 let me know what changes you'd recommend and I'll see how feasable they
  44 are.
  45
  46   --Andrew Church
  47     <A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>
  48     <A HREF="http://achurch.org/">http://achurch.org/</A>
  49
  50 &gt;<i>Hi! After a bit of a hiatus for DebConf, I'm catching up with my
  51 </I>&gt;<i>packaging work.
  52 </I>&gt;<i>
  53 </I>&gt;<i>I've worked out three changes that I'd like to make for Debian:
  54 </I>&gt;<i>
  55 </I>&gt;<i>      * You may have noticed that the consensus on the Debian bug
  56 </I>&gt;<i>        tracker is that I need to change the package name to something
  57 </I>&gt;<i>        other than 'ircservices' to fit into the package namespace - so
  58 </I>&gt;<i>        I'd like to change the binary name as well. Currently the value
  59 </I>&gt;<i>        of $(PROGRAM) in the Makefile doesn't affect the pidfile or the
  60 </I>&gt;<i>        ircservices-chk script.
  61 </I>&gt;<i>      * I need to be able to change the build prefix independently for
  62 </I>&gt;<i>        'make install' - i.e. as if installing into a chroot. I could
  63 </I>&gt;<i>        either add an $(INSTALL_PREFIX) variable, or possibly modify
  64 </I>&gt;<i>        $(PREFIX) in a backwards-compatible way.
  65 </I>&gt;<i>      * The default locations of the installed files will need modifying
  66 </I>&gt;<i>        to fit into the Filesystem Hierarchy Standard. This will be the
  67 </I>&gt;<i>        most complicated patch, I expect.
  68 </I>&gt;<i>
  69 </I>&gt;<i>I realise this is at a really bad time in your release process, so if I
  70 </I>&gt;<i>don't get all of these done in time, I can maintain patches against the
  71 </I>&gt;<i>released version.
  72 </I>&gt;<i>
  73 </I>&gt;<i>Thanks,
  74 </I>&gt;<i>
  75 </I>&gt;<i>--
  76 </I>&gt;<i>Tim Retout &lt;<A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">tim at retout.co.uk</A>&gt;
  77 </I>&gt;<i>
  78 </I>&gt;<i>------------------------------------------------------------------
  79 </I>&gt;<i>To unsubscribe or change your subscription options, visit:
  80 </I>&gt;<i><A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding</A>
  81 </I></PRE>
  82
  83
  84 <!--endarticle-->
  85     <HR>
  86     <P><UL>
  87         <!--threads-->
  88         <LI>Previous message: <A HREF="003302.html">[IRCServices Coding] Build prefix/FHS compliance
  89 </A></li>
  90         <LI>Next message: <A HREF="003304.html">[IRCServices Coding] Build prefix/FHS compliance
  91 </A></li>
  92          <LI> <B>Messages sorted by:</B>
  93               <a href="date.html#3303">[ date ]</a>
  94               <a href="thread.html#3303">[ thread ]</a>
  95               <a href="subject.html#3303">[ subject ]</a>
  96               <a href="author.html#3303">[ author ]</a>
  97          </LI>
  98        </UL>
  99
 100 </body></html>