Re: Handling flat_namespace on 10.10+

Jack Howarth <[email protected]>
Newsgroups gmane.os.apple.fink.devel
Message-ID <CAP5Ds0DTPNxwegVSNienYTsWOBWYBMeT+7zDt8gCU4_KX+YK1A@mail.gmail.com>
Since this issue is so rare (only openmpi and libXt require
flat_namepace...with the latter being an historical artifact to keep
motif working), why not check the package name as they are processed
and if it skip the flat_namespace check if the package name matches
openmpi-shlibs_*.deb or openmpi_*.deb? Ugly but it will suffice.

On Tue, Apr 28, 2015 at 12:20 PM, Alexander Hansen
<[email protected]> wrote:
>
>> On Apr 28, 2015, at 08:41, Jack Howarth <[email protected]> wrote:
>>
>> Are the checks for the shlibs in Validation.pm done for the files from
>> all packages at once or as sets for each package and/or its
>> split-offs? If the latter, what about the idea of hard-coding a
>> blacklist into Validation.pm of packages and/or split-off which should
>> be skipped?
>>
>
> It’s the latter.  .info file validation is done as a batch, but the .deb validator works package by package—ideally only the root directories for the package family currently being built would even be available for validation during the build operation.
> --
> Alexander Hansen, Ph.D.
> Fink User Liaison
>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.