From: Mark Geisert <mark@maxrnd.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] cygutils
Date: Thu, 19 Nov 2015 10:04:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.63.1511190158130.13045@m0.truegem.net> (raw)
In-Reply-To: <20151116094336.GA2585@calimero.vinschen.de>
On Mon, 16 Nov 2015, Corinna Vinschen wrote:
> Packaging looks good. Just one nit: While this is as Chuck did it way
> back when, I think the files under /usr/share/doc should go into the
> base cygutils package, rather than the cygutils-extra package, i.e.
>
> usr/share/doc/cygutils/AUTHORS
> usr/share/doc/cygutils/ChangeLog
> usr/share/doc/cygutils/COPYING
> usr/share/doc/cygutils/HOW-TO-CONTRIBUTE
> usr/share/doc/cygutils/licenses/
> usr/share/doc/cygutils/licenses/COPYING.BSD-no-advert
> usr/share/doc/cygutils/licenses/COPYING.GPLv2
> usr/share/doc/cygutils/licenses/COPYING.GPLv3
> usr/share/doc/cygutils/NEWS
> usr/share/doc/cygutils/PROGLIST
> usr/share/doc/cygutils/README
> usr/share/doc/cygutils/TODO
>
> should be in the cygutils package, while
>
> usr/share/doc/cygutils/cygicons/
> usr/share/doc/cygutils/cygicons/README
> usr/share/doc/cygutils/lpr/
> usr/share/doc/cygutils/lpr/README
>
> should stay in cygutils-extra.
>
> That's a minor point and at your discretion, otherwise GTG.
I agree and have adjusted the packaging as you suggested.
>> Something I don't understand yet is why, when using this cygutils.cygport,
>> some cygport commands download the source from sourceware via git, while
>> other commands seem to want the .tar.bz2 file. The cygutils.cygport is
>> possibly not completely right yet.
>
> You have both, a SRC_URI and a GIT_URI. This might confuse cygport.
> Drop the SRC_URI and only keep GIT_URI.
Even with that change 'cygport all' wants the .tar.bz2 file to be present.
Maybe my mistake is assuming "all" means pull the source too? If I do
'cygport fetch all' it works like a charm using the Git tree, so I'll just
keep doing that.
..mark
next prev parent reply other threads:[~2015-11-19 10:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 19:50 Mark Geisert
2015-10-27 10:00 ` Corinna Vinschen
2015-10-28 0:51 ` Andrew Schulman
[not found] ` <jv603b9c52n950pinp5tmd2ut <pc623bl4g7k2m1lg605ehcce3d09o63lk3@4ax.com>
[not found] ` <pc623bl4g7k2m1lg605ehcce3d09o63lk3-e09XROE/p8c@public.gmane.org>
2015-10-28 13:31 ` Corinna Vinschen
2015-10-28 18:54 ` Andrew Schulman
2015-10-28 22:41 ` Mark Geisert
2015-10-28 23:04 ` Andrew Schulman
2015-10-29 8:32 ` Corinna Vinschen
2015-10-30 14:48 ` Andrew Schulman
2015-10-30 19:24 ` Corinna Vinschen
2015-11-16 5:39 ` Mark Geisert
2015-11-16 5:42 ` Mark Geisert
2015-11-16 6:02 ` Mark Geisert
2015-11-16 9:43 ` Corinna Vinschen
2015-11-19 10:04 ` Mark Geisert [this message]
2015-11-19 10:35 ` Corinna Vinschen
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=Pine.BSF.4.63.1511190158130.13045@m0.truegem.net \
--to=mark@maxrnd.com \
--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).