On Thu, 28 Mar 2019 22:33:48, Thomas Wolff wrote:
It's a bit strange that you're telling my that *you* don't care about
*my* information.
I'm trying to raise some awareness about privacy on this occasion (which
is quite a topic nowadays) and if you don't care, you don't need to comment.
Yeah,
Am 28.03.2019 um 20:47 schrieb Achim Gratz:
Thomas Wolff writes:
I do not like the dual chaos of manual vs info pages, and I'm maybe a
bit old-fashioned to insist that manual pages should be complete, but
isn't that their purpose?
You are barking up the wrong tree, but if you're that bothered b
Am 28.03.2019 um 19:38 schrieb Vince Rice:
On Mar 28, 2019, at 1:33 PM, Thomas Wolff wrote:
Am 28.03.2019 um 19:16 schrieb Vince Rice:
On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
A potential solution is, add another user to your system named cygwin.
When you build you packages use the cy
Thomas Wolff writes:
> I do not like the dual chaos of manual vs info pages, and I'm maybe a
> bit old-fashioned to insist that manual pages should be complete, but
> isn't that their purpose?
You are barking up the wrong tree, but if you're that bothered by it,
you can file an RFE or bug report w
> On Mar 28, 2019, at 1:33 PM, Thomas Wolff wrote:
>
> Am 28.03.2019 um 19:16 schrieb Vince Rice:
>>> On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
>>>
A potential solution is, add another user to your system named cygwin.
When you build you packages use the cygwin user. The debug in
Am 28.03.2019 um 19:16 schrieb Vince Rice:
On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
A potential solution is, add another user to your system named cygwin.
When you build you packages use the cygwin user. The debug information
will reference your cygwin user, and not your real user accou
Am 28.03.2019 um 19:21 schrieb Achim Gratz:
Thomas Wolff writes:
In fact that seems to work, although there is no TAR_OPTIONS
documented in the manual page.
The already much too long manual page does tell you to consult the info
manual right at the top, does it not?
I do not like the dual chaos
On 2019-03-28 7:36 am, Steven Penny wrote:
On Thu, 28 Mar 2019 08:34:34, Thomas Wolff wrote:
Mintty can be used to run any command-line application directly (like
top, your editor, ...), a shell is not needed.
That may be true, the by default Mintty is configure to load Bash. So
it is
disinge
Thomas Wolff writes:
> In fact that seems to work, although there is no TAR_OPTIONS
> documented in the manual page.
The already much too long manual page does tell you to consult the info
manual right at the top, does it not?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andro
> On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
>
>> A potential solution is, add another user to your system named cygwin.
>> When you build you packages use the cygwin user. The debug information
>> will reference your cygwin user, and not your real user account.
> Thanks for the suggestion,
Am 28.03.2019 um 15:02 schrieb Jeffrey Walton:
On Thu, Mar 28, 2019 at 4:44 AM Thomas Wolff wrote:
...
Björn Stabel wrote:
On 27/03/2019 23:59, Yaakov Selkowitz wrote:
On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
I used to use tar rather than cygport package to generate the package
Am 28.03.2019 um 18:40 schrieb Achim Gratz:
Björn Stabel writes:
Sorry for commenting from the peanut gallery, but his problem may be
that he doesn't want to disclose his user name to anyone nosy enough to
snoop around in the package files.
Not tested, but something like
env TAR_OPTIONS="--use
Björn Stabel writes:
> Sorry for commenting from the peanut gallery, but his problem may be
> that he doesn't want to disclose his user name to anyone nosy enough to
> snoop around in the package files.
Not tested, but something like
env TAR_OPTIONS="--user=0 --group=0" cygport ...
should do it.
Thomas Wolff writes:
> Mintty can be used to run any command-line application directly (like
> top, your editor, ...), a shell is not needed.
Your _package_ has a dependency to the shell by way of including a shell
script. If you so desperately want to get rid of it (even though it's
always insta
On 2019-03-28 05:36, Steven Penny wrote:
> On Thu, 28 Mar 2019 08:34:34, Thomas Wolff wrote:
>> Mintty can be used to run any command-line application directly (like top,
>> your editor, ...), a shell is not needed.
>
> That may be true, the by default Mintty is configure to load Bash. So it is
>
On Thu, Mar 28, 2019 at 4:44 AM Thomas Wolff wrote:
> ...
> Björn Stabel wrote:
> > On 27/03/2019 23:59, Yaakov Selkowitz wrote:
> >> On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
> >>> I used to use tar rather than cygport package to generate the packages.
> >>> One reason was that I did
On Thu, 28 Mar 2019 08:34:34, Thomas Wolff wrote:
Mintty can be used to run any command-line application directly (like
top, your editor, ...), a shell is not needed.
That may be true, the by default Mintty is configure to load Bash. So it is
disingenuous so simply say that it does not require
On Mar 28 09:43, Thomas Wolff wrote:
> Achim Gratz wrote:
> >
> > > Trying cygport package, a bunch of problems arise:
> > >
> > > I removed -s as suggested by Achim, added -g as advised by Corinna,
> > > but cygport still says:
> > > *** Info: No debug files, skipping debuginfo subpackage
> > We
Achim Gratz wrote:
Trying cygport package, a bunch of problems arise:
I removed -s as suggested by Achim, added -g as advised by Corinna,
but cygport still says:
*** Info: No debug files, skipping debuginfo subpackage
Well, do not reset CFLAGS in your Makefile and cygport helpfully
provides a
Am 28.03.2019 um 04:42 schrieb Steven Penny:
On Wed, 27 Mar 2019 20:44:44, Brian Inglis wrote:
Both dash and bash are in Base, installed by default, and both are login
shells, while dash requires only cygwin1.dll to run, and can be used
during
setup, before other libraries or utilities are ins
On 27/03/2019 23:59, Yaakov Selkowitz wrote:
> On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
>> I used to use tar rather than cygport package to generate the packages.
>> One reason was that I didn’t want my local user/group to appear in them.
> They won't show up like that once installed.
On Wed, 27 Mar 2019 20:44:44, Brian Inglis wrote:
Both dash and bash are in Base, installed by default, and both are login
shells, while dash requires only cygwin1.dll to run, and can be used during
setup, before other libraries or utilities are installed.
Yeah, I did not mean to say login shel
On 2019-03-27 19:12, Steven Penny wrote:
> On Wed, 27 Mar 2019 19:09:07, Yaakov Selkowitz wrote:
>> "Only" if /bin/bash is your preferred shell. Granted, that's the
>> default, and what most users would want anyway, but that is not
>> strictly speaking a mintty dependency. As I mentioned in my re
On Wed, 2019-03-27 at 18:12 -0700, Steven Penny wrote:
> On Wed, 27 Mar 2019 19:09:07, Yaakov Selkowitz wrote:
> > "Only" if /bin/bash is your preferred shell. Granted, that's the
> > default, and what most users would want anyway, but that is not
> > strictly speaking a mintty dependency. As I m
On Wed, 27 Mar 2019 19:09:07, Yaakov Selkowitz wrote:
"Only" if /bin/bash is your preferred shell. Granted, that's the
default, and what most users would want anyway, but that is not
strictly speaking a mintty dependency. As I mentioned in my response,
the auto-detected dependency on bash is fr
On Wed, 2019-03-27 at 15:51 -0700, Steven Penny wrote:
> On Wed, 27 Mar 2019 21:02:47, Thomas Wolff wrote:
> > >>> mintty requires: bash cygwin
> > I remember some discussion that the cygwin dependency, which most
> > packages have, should not (or does not need to be) listed.
> > And in fact, min
On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
> Am 25.03.2019 um 19:12 schrieb Achim Gratz:
> > Thomas Wolff writes:
> > > Sorry, I neither know how to make use of such a package nor how to
> > > generate it or what it contains.
> > > But I'd take a patch:)
> > As you wish…
> I used to use
On Wed, 27 Mar 2019 21:02:47, Thomas Wolff wrote:
>>> mintty requires: bash cygwin
I remember some discussion that the cygwin dependency, which most
packages have, should not (or does not need to be) listed.
And in fact, mintty does not depend on bash. Why does cygport think so?
Uh, Mintty d
On Wed, Mar 27, 2019 at 4:36 PM Achim Gratz wrote:
> ...
> > I removed -s as suggested by Achim, added -g as advised by Corinna,
> > but cygport still says:
> > *** Info: No debug files, skipping debuginfo subpackage
>
> Well, do not reset CFLAGS in your Makefile and cygport helpfully
> provides a
Thomas Wolff writes:
> I used to use tar rather than cygport package to generate the packages.
> One reason was that I didn’t want my local user/group to appear in them.
> Is that possible with cygport?
PTC. But yes, I think GNU Tar has an option to override those, cygport
is just not using it ye
Am 25.03.2019 um 19:12 schrieb Achim Gratz:
Thomas Wolff writes:
Sorry, I neither know how to make use of such a package nor how to
generate it or what it contains.
But I'd take a patch:)
As you wish…
I used to use tar rather than cygport package to generate the packages.
One reason was that I
Thomas Wolff writes:
> Sorry, I neither know how to make use of such a package nor how to
> generate it or what it contains.
> But I'd take a patch:)
As you wish…
mintty.cygport
Description: Binary data
--- origsrc/mintty-2.9.9/src/Makefile 2019-03-16 07:13:38.0 +0100
+++ src/mintty-2.9
On Mar 25 00:36, Thomas Wolff wrote:
> Hi Corinna,
>
> Am 24.03.2019 um 19:19 schrieb Corinna Vinschen:
> > On Mar 24 16:57, Thomas Wolff wrote:
> > > Hi Achim,
> > >
> > > Am 16.03.2019 um 15:00 schrieb Achim Gratz:
> > > > Thomas Wolff writes:
> > > > > I have uploaded mintty 2.9.9 with the fol
Hi Corinna,
Am 24.03.2019 um 19:19 schrieb Corinna Vinschen:
On Mar 24 16:57, Thomas Wolff wrote:
Hi Achim,
Am 16.03.2019 um 15:00 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.9.9 with the following changes:
While you're at it, could you please stop using the release n
Greetings, Thomas Wolff!
> Am 16.03.2019 um 15:00 schrieb Achim Gratz:
>> Thomas Wolff writes:
>>> I have uploaded mintty 2.9.9 with the following changes:
>> While you're at it, could you please stop using the release number "0" for
>> your packages?
> I had previously explained why I used to li
On Mar 24 16:57, Thomas Wolff wrote:
> Hi Achim,
>
> Am 16.03.2019 um 15:00 schrieb Achim Gratz:
> > Thomas Wolff writes:
> > > I have uploaded mintty 2.9.9 with the following changes:
> > While you're at it, could you please stop using the release number "0" for
> > your packages?
> I had previo
On 2019-03-24 09:57, Thomas Wolff wrote:
> Am 16.03.2019 um 15:00 schrieb Achim Gratz:
>> Thomas Wolff writes:
>>> I have uploaded mintty 2.9.9 with the following changes:
>> While you're at it, could you please stop using the release number "0" for
>> your packages?
> I had previously explained wh
Hi Achim,
Am 16.03.2019 um 15:00 schrieb Achim Gratz:
Thomas Wolff writes:
I have uploaded mintty 2.9.9 with the following changes:
While you're at it, could you please stop using the release number "0" for your
packages?
I had previously explained why I used to like this (native package, no
On Sat, 16 Mar 2019 15:00:54, Achim Gratz wrote:
Thomas Wolff writes:
I have uploaded mintty 2.9.9 with the following changes:
While you're at it, could you please stop using the release number "0"
for your packages? That's supposed to be used for test packages only
(if you want to make an ef
Thomas Wolff writes:
> I have uploaded mintty 2.9.9 with the following changes:
While you're at it, could you please stop using the release number "0"
for your packages? That's supposed to be used for test packages only
(if you want to make an effort to convey that in the package file name).
Prop
I have uploaded mintty 2.9.9 with the following changes:
Keyboard handling
* Fixed modifyOtherKeys mode 1 to use verbatim control keys.
The homepage is at http://mintty.github.io/
It also links to the issue tracker.
--
Thomas
--
Problem reports: http://cygwin.com/problems.html
FAQ:
41 matches
Mail list logo
