This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Base Cygwin now requires Python?
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 17 May 2013 01:58:13 -0400
- Subject: Re: Base Cygwin now requires Python?
- References: <CAAXzdLVNdced57cNh=C0tR7JYtC+DaXceB_gapFjb-GJy01Rrw at mail dot gmail dot com> <CAHWeT-a3ukL9y=BBnCoK0zKw-h_v2gXFo4ycQs4_NJavrC8MUw at mail dot gmail dot com> <20130516225955 dot GA5505 at ednor dot casa dot cgf dot cx> <CAHWeT-YLTY56Gg_PpAyVtbdev3Eh0QicTwzbho_Kg6X7bYpzeg at mail dot gmail dot com>
- Reply-to: cygwin-apps at cygwin dot com
On Fri, May 17, 2013 at 05:41:05AM +0100, Andy Koppe wrote:
>On 16 May 2013 23:59, Christopher Faylor wrote:
>> On Thu, May 16, 2013 at 07:39:59PM +0100, Andy Koppe wrote:
>>>On 16 May 2013 07:41, Steven Penny wrote:
>>>> Because of this dependency line
>>>>
>>>> mintty
>>>> cygutils
>>>
>>>Hmm, mintty doesn't depend on cygutils anymore since setup.exe creates
>>>the "Cygwin Terminal" shortcut for it, and its setup.hint reflects
>>>that. Yet setup.ini does indeed contain the following line for mintty:
>>>
>>>requires: bash cygutils cygwin
>>>
>>>Is the problem that the setup.hint doesn't contain a 'requires:' line
>>>at all (since mintty has no dependencies apart from the implicit
>>>'cygwin')? Does upset keep previous dependencies in that case?
>>
>> What??? No! Of course it doesn't! What a daft notion!
>>
>> Oh. Actually, now that I think of it, the way upset is run, it's the
>> union of an existing setup.ini and setup.hint. So, if there is no
>> requires: line it would get pulled from setup.ini.
>>
>> I've taken the liberty of adding a "requires:" line to mintty's setup.hint.
>
>Thanks, I've updated the copy in mintty svn accordingly.
I've confirmed that setup.exe now has a blank requires line.
Hmm. Actually, I think that means that the requires line could actually
be deleted since upset will no longer try to use the line from
setup.ini.