This is the mail archive of the
mailing list for the Cygwin project.
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 25 Jun 2015 18:40:18 +0200
- Subject: Re: setup
- Authentication-results: sourceware.org; auth=none
- References: <874mmghlf8 dot fsf at Rainer dot invalid> <20150610080526 dot GC31537 at calimero dot vinschen dot de> <871thjtq0m dot fsf at Rainer dot invalid> <20150610185417 dot GL31537 at calimero dot vinschen dot de> <87wpzbs2yj dot fsf at Rainer dot invalid> <87mw060xg3 dot fsf at Rainer dot invalid> <20150612102945 dot GS31537 at calimero dot vinschen dot de> <87bngkzwki dot fsf at Rainer dot invalid> <20150612173704 dot GB28638 at calimero dot vinschen dot de> <87ioacnag7 dot fsf at Rainer dot invalid> <20150625085933 dot GO31223 at calimero dot vinschen dot de>
Corinna Vinschen writes:
> Having said that, any more intelligent algorithm searching only where it
> actually makes sense, would be real progress. More C than C++ wouldn't
> hurt either.
The pattern is just misapplied in this particular case, trying to take a
gatherer on a hunt.
> I'm not sure I understand what you're saying. Setup.ini should never be
> at the local package directory level is my understanding.
Great, then I can just skip that wierdness of the old code.
> Strictly, we don't have to support updates from the old non-multi-arch
> setup anymore, therefore any top-level setup.ini can be ignored.
> So, from my POV, the search should ideally work like this:
> - Start at Local package directory.
> - Look if a $arch subdir exists. If so, does it have setup.ini?
> If so collect it and stop here.
> - Otherwise search all immediate subdirs. Look if they have a
> $arch subdir. If so, does it have setup.ini? If so, collect it.
> Does that make sense?
Yes and I just have to rip out the compat code that dealt with the other
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: