What about a fink flag that would allow certain stages of validation to be skipped. Something like --disable-validation= where it could be passed the major stages like deb, etc.
On Tue, Apr 21, 2015 at 3:14 PM, Hanspeter Niederstrasser <f...@snaggledworks.com> wrote: > > On Thu, April 16, 2015 11:46 am, Alexander Hansen wrote: >> Summary: GNU libtool effectively assumed that there would be no 10.10, so >> a bunch of packages inherited conditional logic that treats 10.10 like >> 10.1. We’ve been patching against this, and put a .deb validator check >> for flat_namespace builds. >> >> Problem: openmpi apparently requires flat_namespace. Other packages >> might also need it, too, but I don’t happen to know of any offhand. >> >> There are a couple of options to address the problem: >> >> 1) Add a boolean override field, e.g. BuildFlatNamespace, to the .info >> and have that turn off the .deb validation check. > > This seems like a gateway to propagating new fields with very limited > usage. The last couple of new fields (RuntimeDepends, NoBuildAsNobody, > etc) had a significantly wider need. So far BuildFlatNamespace has N=1. > Would it make more sense to have a new more general field that can receive > a comma separated list of pre-set values, and each value would indicate a > action? > > RandomTidbitField: AllowFlatNamespace, ThwackUserWithTuna > > Could Type: be extended in this manner? > >> 2) Get rid of the .deb validation check and instead apply mandatory tests >> in the earlier phases. For example, to test at the end of the compile >> phase fink-package-precedence could be extended also to check for >> flat_namespace and packages which need flat_namespace wouldn’t use >> f-p-p; or an additional option flag could be added to f-p-p. We could >> also check config.status before the compile phase. > > Would built debs still be validatable (by hand)? > > Hanspeter > > -- > More agile than a turtle, stronger than a mouse, nobler than a lettuce > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > Fink-devel mailing list > Fink-devel@lists.sourceforge.net > List archive: > http://news.gmane.org/gmane.os.apple.fink.devel > Subscription management: > https://lists.sourceforge.net/lists/listinfo/fink-devel ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
