unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Aljosha Papsch <lists@rpapsch.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add httpd
Date: Sun, 29 Sep 2013 19:19:29 +0200	[thread overview]
Message-ID: <877gdzilzy.fsf@gnu.org> (raw)
In-Reply-To: <1380465751.25677.5.camel@creek.rivers> (Aljosha Papsch's message of "Sun, 29 Sep 2013 16:42:31 +0200")

Hi,

Thanks for joining the hackathon!

Aljosha Papsch <lists@rpapsch.de> skribis:

> attached is a patch for Apache httpd.  I named the module web, so other
> web servers might go in there (maybe merge in libmicrohttpd?).

Yes, makes sense.

> I hope the format is alright. It's just the output of git format-patch.

It’s good overall.  Just a couple of minor suggestions in-line, and then
we can commit it:

> From a54ae468ab008bad21e5d1069ee36a0eaa0ee40a Mon Sep 17 00:00:00 2001
> From: Aljosha Papsch <misc@rpapsch.de>
> Date: Sun, 29 Sep 2013 16:30:19 +0200
> Subject: [PATCH] gnu: Add httpd * gnu/packages/web.scm (httpd): New variable *
>  gnu-system.am (GNU_SYSTEM_MODULES): Add it

Please just write just “Add httpd” in the subject line, and write the
rest of the log in the body, one line per thing.

Here’s an example:

> +(define-public httpd
> +  (package
> +   (name "httpd")
> +   (version "2.4.6")
> +   (source (origin
> +	    (method url-fetch)
> +	    (uri (string-append "mirror://apache/httpd/httpd-"
> +				version ".tar.bz2"))
> +	    (sha256
> +	     (base32
> +	      "1sig08xxq1kqxr2a42ndwr9g4mm6zdqnxldhxraym2y0xcjkd7yw"))))

Please do not use tabs in .scm files (for Emacs there’s a .dir-locals.el
file that should set it up.)

> +   (arguments
> +    `(#:tests? #f

Usually we try to fix any test suite issues, but sometimes we end up
disabling it altogether when that’s really too much effort or when we’re
waiting for feedback from upstream.

What problems did you encounter?  A typical issue with networking
packages is that tests try to perform DNS lookups, which doesn’t work in
our chroot build environment.  Often that can be worked around, for
instance by replacing ‘localhost’ with ‘127.0.0.1’.

> +      #:configure-flags (list "--enable-rewrite"
> +                              "--enable-userdir"
> +                              "--enable-vhost-alias"
> +                              "--enable-ssl"
> +                              "--enable-mime-magic"
> +                              (string-append "--sysconfdir="
> +                                             (assoc-ref %outputs "out")
> +                                             "/etc/httpd"))))
> +   (synopsis "A robust, commercial-grade, featureful HTTP server")

“Featureful HTTP server” should be enough.

Thanks!

Ludo’.

  reply	other threads:[~2013-09-29 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 14:42 [PATCH] gnu: Add httpd Aljosha Papsch
2013-09-29 17:19 ` Ludovic Courtès [this message]
2013-09-29 18:26   ` Ludovic Courtès
2013-09-29 19:01   ` Aljosha Papsch

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877gdzilzy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=lists@rpapsch.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).