On 2016-09-17 13:23, Achim Gratz wrote:
I've reworked the original patch by David ROthenberger to use
override.hint so it'll keep working with calm.
I still don't like this concept. But now that we have per-version
hints, could calm be changed to accept e.g. a test: tag in such, the
latest
> On 16/09/2016 11:15, Andrew Schulman wrote:
> >> Andrew Schulman writes:
> >>> Hi Marco. I think I thought about this in the past, but because the total
> >>> size of this package is so small, I decided it wasn't worth the trouble to
> >>> split it in two. I think that both packages would have
On 18/09/2016 19:16, Achim Gratz wrote:
Marco Atzeri writes:
I suggest to remove the requirements.
The main list have in automatic:
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Marco Atzeri writes:
> I suggest to remove the requirements.
>
> The main list have in automatic:
>
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info:
On 18/09/2016 18:41, Ken Brown wrote:
Another thing: The page still says that all release announcements should
contain information about unsubscribing from the cygwin-announce mailing
list. But it seems that many (most?) maintainers have stopped doing
this. And 'cygport announce' doesn't do
On 9/18/2016 11:14 AM, Jon Turney wrote:
On 18/09/2016 06:17, Marco Atzeri wrote:
On 17/09/2016 08:14, Achim Gratz wrote:
Jon Turney writes:
Currently, the setup.hint file is shared between all versions.
This means that manual intervention (by the package maintainer, or on
sourceware) is
Achim Gratz writes:
> Jon Turney writes:
>> I notice the section about postinstall scripts doesn't mention
>> permanent postinsall scripts at all.
>>
>> Could you possibly provide a couple of paragraphs?
>
> I had sent them to this very list at the time. I need to dig them out
> of the archive
I've compiled minicom for Cygwin for my own use. I'm intending to
package it, but there is a bug that stumps my ability to debug: Opening
the help screen makes minicom exit, which kind of defeats the purpose.
If you press any key before the help screen is fully open, minicom
continues to run and
Jon Turney writes:
> I notice the section about postinstall scripts doesn't mention
> permanent postinsall scripts at all.
>
> Could you possibly provide a couple of paragraphs?
I had sent them to this very list at the time. I need to dig them out
of the archive unless you're faster.
Regards,
On 18/09/2016 06:17, Marco Atzeri wrote:
On 17/09/2016 08:14, Achim Gratz wrote:
Jon Turney writes:
Currently, the setup.hint file is shared between all versions.
This means that manual intervention (by the package maintainer, or on
sourceware) is needed when versions have different
10 matches
Mail list logo
