software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2007/003302.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=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="003298.html">
  11    <LINK REL="Next"  HREF="003303.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] Build prefix/FHS compliance</H1>
  15     <B>Tim Retout</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Build%20prefix/FHS%20compliance&In-Reply-To="
  17        TITLE="[IRCServices Coding] Build prefix/FHS compliance">tim at retout.co.uk
  18        </A><BR>
  19     <I>Fri Jul 13 03:18:39 PDT 2007</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="003298.html">[IRCServices Coding] RE: IRCServices-Coding Digest, Vol 33,
  22         Issue 1
  23 </A></li>
  24         <LI>Next message: <A HREF="003303.html">[IRCServices Coding] Build prefix/FHS compliance
  25 </A></li>
  26          <LI> <B>Messages sorted by:</B>
  27               <a href="date.html#3302">[ date ]</a>
  28               <a href="thread.html#3302">[ thread ]</a>
  29               <a href="subject.html#3302">[ subject ]</a>
  30               <a href="author.html#3302">[ author ]</a>
  31          </LI>
  32        </UL>
  33     <HR>
  34 <!--beginarticle-->
  35 <PRE>Hi! After a bit of a hiatus for DebConf, I'm catching up with my
  36 packaging work.
  37
  38 I've worked out three changes that I'd like to make for Debian:
  39
  40       * You may have noticed that the consensus on the Debian bug
  41         tracker is that I need to change the package name to something
  42         other than 'ircservices' to fit into the package namespace - so
  43         I'd like to change the binary name as well. Currently the value
  44         of $(PROGRAM) in the Makefile doesn't affect the pidfile or the
  45         ircservices-chk script.
  46       * I need to be able to change the build prefix independently for
  47         'make install' - i.e. as if installing into a chroot. I could
  48         either add an $(INSTALL_PREFIX) variable, or possibly modify
  49         $(PREFIX) in a backwards-compatible way.
  50       * The default locations of the installed files will need modifying
  51         to fit into the Filesystem Hierarchy Standard. This will be the
  52         most complicated patch, I expect.
  53
  54 I realise this is at a really bad time in your release process, so if I
  55 don't get all of these done in time, I can maintain patches against the
  56 released version.
  57
  58 Thanks,
  59
  60 --
  61 Tim Retout &lt;<A HREF="http://lists.ircservices.za.net/mailman/listinfo/ircservices-coding">tim at retout.co.uk</A>&gt;
  62
  63 </PRE>
  64
  65
  66 <!--endarticle-->
  67     <HR>
  68     <P><UL>
  69         <!--threads-->
  70         <LI>Previous message: <A HREF="003298.html">[IRCServices Coding] RE: IRCServices-Coding Digest, Vol 33,
  71         Issue 1
  72 </A></li>
  73         <LI>Next message: <A HREF="003303.html">[IRCServices Coding] Build prefix/FHS compliance
  74 </A></li>
  75          <LI> <B>Messages sorted by:</B>
  76               <a href="date.html#3302">[ date ]</a>
  77               <a href="thread.html#3302">[ thread ]</a>
  78               <a href="subject.html#3302">[ subject ]</a>
  79               <a href="author.html#3302">[ author ]</a>
  80          </LI>
  81        </UL>
  82
  83 </body></html>