This is the mail archive of the cygwin-apps mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |