From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: cygport: Request a new feature in order to set owner/group names in packaged tarballs.
Date: Fri, 07 Aug 2020 21:09:11 +0200 [thread overview]
Message-ID: <87bljm1dew.fsf@Otto.invalid> (raw)
In-Reply-To: <20200807233351.4B7D.50F79699@gmail.com> (Lemures Lemniscati via Cygwin-apps's message of "Fri, 07 Aug 2020 23:33:53 +0900")
Lemures Lemniscati via Cygwin-apps writes:
>> No, I was talking about things like XZ_OPT or ZSTD_CLEVEL.
>
> I think XZ_OPT or ZSTD_CLEVEL can be passed through environment.
> And this should control xz or zstd..
>
> XZ_OPT="..." cygport foo.cygport package
> ZSTD_CLEVEL="..." cygport foo.cygport package
>
> And cygport does not prevent from passing parameter through environment.
> Maybe I understand you in a wrong way. Pardon me.
Maybe if you'd gone back to the post I sent on June 14 when I originally
offered the patch you'd have seen:
>> This patch keeps the current defaults in place, but allows one to set up
>> two environment variables to control how tar gets invoked during
>> packaging. You could do that from either the cygport file or the
>> .cygport.conf file:
>>
>> CYGPORT_TAR_CMD="env ZSTD_CLEVEL=19 tar -I zstd --group nobody:65534 --owner nobody:65534"
>> CYGPORT_TAR_EXT=".tar.zst"
I don't want to pollute the environment for any other command obviously…
and really, I still think creating five new configuration variables to
do what can be accomplished with two isn't a good trade-off.
Factoring out the command invocation into a function probably is a net
win, though -- so I'd keep that part. It'd probably be useful in some
other instances to so a similar refactoring.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2020-08-07 19:09 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
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 [this message]
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=87bljm1dew.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).