guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gnu: Add darkhttpd.


From: Leo Famulari
Subject: Re: [PATCH] gnu: Add darkhttpd.
Date: Tue, 13 Sep 2016 11:42:43 -0400
User-agent: Mutt/1.7.0 (2016-08-17)

On Mon, Sep 12, 2016 at 12:50:14AM +0530, Arun Isaac wrote:
> * gnu/packages/web.scm (darkhttpd): New variable.

Thanks for this patch!

> +    (version "1.12")
> +    (source
> +     (origin
> +       ;; The darkhttpd release tarball URL fails to download with a
> +       ;; 'TLS warning alert'. Download from the darkhttpd git repo
> +       ;; until the problem has been fixed upstream.
> +       (method git-fetch)
> +       (uri (git-reference
> +             (url (string-append "https://unix4lyfe.org/git/darkhttpd";))
> +             (commit "master")))

If I understand correctly, this will not work as expected. When the
master branch gets another commit, our package's hash will become
invalid.

Too bad upstream doesn't make Git tags for their releases. Commit
41b68476c35270f47dcd2ddebe27cbcd87e43d41 appears to correspond to the
1.12 release, so we should specify that commit:

https://unix4lyfe.org/gitweb/darkhttpd/commit/41b68476c35270f47dcd2ddebe27cbcd87e43d41

> +         (replace 'install
> +           (lambda* (#:key outputs #:allow-other-keys)
> +             (install-file "darkhttpd"
> +                           (string-append (assoc-ref outputs "out")
> +                                          "/bin"))
> +             #t)))))

Did you notice if there is any documentation that could be installed too?

In any case, can you send a revised patch addressing the commit /
version issue?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]