From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygport: Request a new feature in order to set owner/group names in packaged tarballs.
Date: Mon, 10 Aug 2020 12:42:02 +0900 [thread overview]
Message-ID: <20200810124159.D23F.50F79699@gmail.com> (raw)
In-Reply-To: <20200808201456.FEA0.50F79699@gmail.com>
On Sat, 08 Aug 2020 20:14:59 +0900, Lemures Lemniscati
> On Sat, 08 Aug 2020 06:32:06 +0200, ASSI
> > Lemures Lemniscati via Cygwin-apps writes:
> > > But I feel uneasy about the usase of CYGPORT_TAR_CMD, because we must
> > > specify 'tar' in it. It is a redundancy.
> >
> > It is also a way to do nefarious things, but there are already many
> > more such places.
> >
> > > The following is a thought experiment to avoid this redundancy.
> > […]
> >
> > As I said, you'll end up with configuration variables for everything
> > except the actual command (which is found in PATH, so if I really wanted
> > to mess with it I could do that anyway).
>
> Oh, I see. My comment was maybe misleading.
>
> My point is that it would be happy for me if it is sufficient to specify
> changed parameters only. (the point is not about avoiding wicked things).
>
> And I guess your point of view about configuration is more general than
> mine.
>
>
> Now, my last wish, in this case, is that these settings, for example,
> would be effective and would do well:
>
> CYGPORT_TAR_EXT=".tar.zst"
> CYGPORT_TAR_CMD="tar -I 'zstd -19 -T0'"
>
> And, I think it will be user-friendly.
>
>
> Regards,
> Lem
Now, I suggest another patch, so that both of the following invocations
work [1].
CYGPORT_TAR_EXT=".tar.zst" CYGPORT_TAR_CMD="env ZSTD_CLEVEL=19 tar -I zstd --group nobody:65534 --owner nobody:65534" cygport foo.cygport package
CYGPORT_TAR_EXT=".tar.zst" CYGPORT_TAR_CMD="tar -I 'zstd -19 -T0' --group nobody:65534 --owner nobody:65534" cygport foo.cygport package
[1]: https://github.com/cygwin-lem/cygport/commit/7ae236b524fa5f5b27f9773cdf21ee4f6624a53b
Regards,
Lem
next prev parent reply other threads:[~2020-08-10 3:42 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
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 [this message]
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=20200810124159.D23F.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.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).