From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Make src packages which put files under /usr/src/package-version-release/
Date: Mon, 28 Apr 2014 12:23:00 -0000 [thread overview]
Message-ID: <535E4824.2040906@dronecode.org.uk> (raw)
In-Reply-To: <535DBE31.1020406@users.sourceforge.net>
On 28/04/2014 03:34, Yaakov (Cygwin/X) wrote:
> On 2014-04-24 15:42, Jon TURNEY wrote:
>> From a previous discussion [1] on this subject, it seems to be that
>> if this is
>> desirable, then source packages should be fixed rather than working
>> around
>> this in setup.
>>
>> Attached is a patch to cygport to do exactly that.
>
> The downside is, if you then rebuild the package like that, you end up
> with /usr/src/NAME-VERSION-RELEASE/NAME-VERSION-RELEASE[.ARCH, as of
> today's git master], which seems a bit repetitive to me. What do you
> (and others) think about making the "topdir" also the "workdir" if the
> former is already of the form NAME-VERSION-RELEASE.ARCH, as per the
> attached patch instead?
I think "workdir" needs to be at least ARCH, otherwise you lose the
(just added) ability to do cygport --32 and cygport --64 in the same
directory?
If I am understanding you correctly, the rest is just a question of
aesthetics. I don't mind the repetition, but others might have a
different opinion.
>> (As an aside, how would a patch to move "Method one" and "Method two"
>> to an
>> archive page be received? It seems to me that they are not relevant
>> to nearly
>> all new packages)
>
> http://cygwin.com/ml/cygwin-apps/2013-06/msg00182.html
Thanks. I guess I'll work on a documentation patch for that, then.
next prev parent reply other threads:[~2014-04-28 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:42 Jon TURNEY
2014-04-28 2:34 ` Yaakov (Cygwin/X)
2014-04-28 12:23 ` Jon TURNEY [this message]
2014-04-28 13:31 ` Ken Brown
2014-05-04 9:10 ` Yaakov (Cygwin/X)
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=535E4824.2040906@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.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).