From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: cygport: Request a new feature in order to set owner/group names in packaged tarballs.
Date: Tue, 4 Aug 2020 15:46:13 +0200 [thread overview]
Message-ID: <f332e0fa-aaec-959a-848d-f5197391f0e9@towo.net> (raw)
In-Reply-To: <20200804215404.5C96.50F79699@gmail.com>
Am 04.08.2020 um 14:54 schrieb Lemures Lemniscati via Cygwin-apps:
> Date: Mon, 03 Aug 2020 21:24:11 +0200
> From: Achim Gratz <Stromeko@nexgo.de>
>
>> Lemures Lemniscati via Cygwin writes:
>>> This is another patch, so that cygport shall make tarballs with
>>> specified owner and group names.
>> Cygport patches should better go to cygwin-apps. I've already sent a
>> patch that allows you to do the same thing some time ago, but it has
>> not been reviewed yet.
>>
>> https://repo.or.cz/cygport/rpm-style.git/commitdiff/c6af2ca23aae5da3e99c70cf2b704430b929f431
>>
> Nice.
>
> Then, how about a commit following yours.
It is much less than obvious in that older patch that you can trick the
owner/group information into that option.
I'd appreciate a simple explicit option for that.
>
> https://github.com/cygwin-lem/cygport/commit/a88f1dfa3619fcf817d558761a5249b09e71cc3c
>
> Now it is suffienct to specify CYGPORT_TAR_EXT as ".tar.zst" in order
> use zstd. But it needs tar version >= 1.31.
>
>
>
> And a next one is for making BUILD_REQUIRES a single-line list in
> *src.hint files.
>
> https://github.com/cygwin-lem/cygport/commit/7607782d3d1972aef6b88ee32f5211f21abbbcfb
next prev parent reply other threads:[~2020-08-04 13:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200803205512.E3F1.50F79699@gmail.com>
[not found] ` <87d047r0ro.fsf@Rainer.invalid>
2020-08-04 12:54 ` Lemures Lemniscati
2020-08-04 13:46 ` Thomas Wolff [this message]
2020-08-04 20:34 ` Lemures Lemniscati
2020-08-05 18:31 ` ASSI
2020-08-05 21:21 ` Lemures Lemniscati
2020-08-06 18:25 ` ASSI
2020-08-07 7:45 ` Thomas Wolff
2020-08-07 14:33 ` Lemures Lemniscati
2020-08-07 19:09 ` ASSI
2020-08-08 0:43 ` Lemures Lemniscati
2020-08-08 4:32 ` ASSI
2020-08-08 11:14 ` Lemures Lemniscati
2020-08-10 3:42 ` Lemures Lemniscati
2020-08-10 19:51 ` Achim Gratz
2020-08-10 21:45 ` Lemures Lemniscati
2020-08-04 17:02 ` ASSI
2020-08-04 20:49 ` Lemures Lemniscati
2020-08-05 19:34 ` Jon Turney
2020-08-05 21:50 ` Lemures Lemniscati
2020-08-06 17:13 ` Jon Turney
2020-08-07 14:43 ` Lemures Lemniscati
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=f332e0fa-aaec-959a-848d-f5197391f0e9@towo.net \
--to=towo@towo.net \
--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).