public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Alexander Georgievskiy <galeksandrp@gmail.com>
Subject: Re: [ITP] polipo 1.1.1
Date: Wed, 19 Apr 2017 18:47:00 -0000	[thread overview]
Message-ID: <6c947980-77f2-f5de-981a-b298b0bcde8c@dronecode.org.uk> (raw)
In-Reply-To: <CAGbjKa1cbFU0QtSwZcTDVGnddNDm+FYxem61avSSVfALOPCxjA@mail.gmail.com>

On 21/03/2017 00:17, Alexander Georgievskiy wrote:
> category: web
> requires: cygwin
> sdesc: "The Polipo caching HTTP proxy"
> ldesc: "Polipo is single-threaded, non blocking caching web proxy that has
> very modest resource needs.  See the file INSTALL for installation
> instructions.  See the texinfo manual (available as HTML after
> installation) for more information."
>
> https://packages.debian.org/jessie/polipo
> https://apps.fedoraproject.org/packages/polipo
> https://software.opensuse.org/package/polipo
> MIT

Sorry about the delay in looking at this.

polipo.cygport:

None of the documentation is packaged.

I think you need to write 'make PREFIX=/usr TARGET=${D} install' rather 
than 'make PREFIX=${D}/usr install' (TARGET seems to have the same 
function as the more usual DESTDIR)

You also need DIFF_EXCLUDES="*.html *.info", to prevent the 
documentation, which is built in the source directory, from being 
identified as patches.

  reply	other threads:[~2017-04-19 18:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21  0:17 Alexander Georgievskiy
2017-04-19 18:47 ` Jon Turney [this message]
2017-04-29  7:20   ` Alexander Georgievskiy
2017-04-29 11:52     ` Jon Turney
     [not found]       ` <CAGbjKa1-MGi3iA6FgcwixkncJEeYiGU4wsuzjn9kvrF+Tg0piA@mail.gmail.com>
2017-05-13 12:02         ` Jon Turney

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

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

  git send-email \
    --in-reply-to=6c947980-77f2-f5de-981a-b298b0bcde8c@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=galeksandrp@gmail.com \
    /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.
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).