> > The output of config.guess is useful for FSF build tools and for doing > > some system-specific checks in configure, and that's pretty much it. > nneul> Well, building architecture specific trees of products could be quite nneul> handy, particularly if you start building versions optimized to nneul> particular CPUs, etc. For this particular one, IMHO you want depot instead; it's ability to present "sparse trees" is a critical requirement that you can't get with a filesystem level mapping. nneul> Or, mapping product trees according to particular environment variable nneul> choices that would be completely transparent to the calling product. Although this sounds like it might be useful, be careful about making the filesystem so complex that you have to be a unix expert to navigate. Even @sys confuses most people for a while... Jim Rowan DCSI [EMAIL PROTECTED]
- OpenAFS: conventions for new @sys? (rs_aix43 s390_linux... Paul Blackburn
- Re: OpenAFS: conventions for new @sys? (rs_aix43 s... Russ Allbery
- Re: OpenAFS: conventions for new @sys? (rs_aix... Russ Allbery
- Re: OpenAFS: conventions for new @sys? (rs... Nathan Neulinger
- Re: OpenAFS: conventions for new @sys?... Russ Allbery
- Re: [OpenAFS-devel] Re: OpenAFS: ... Nathan Neulinger
- Re: [OpenAFS-devel] Re: OpenA... Russ Allbery
- Re: [OpenAFS-devel] Re: OpenA... jmr
- Re: [OpenAFS-devel] Re: O... Russ Allbery
- Re: OpenAFS: conventions for new ... Michael S. Tsirkin
- Re: OpenAFS: conventions for ... Nathan Neulinger
- Re: OpenAFS: conventions ... Bob Cook
- Re: OpenAFS: conventions ... Kelsang Wangden
- Re: OpenAFS: conventions ... R. Lindsay Todd
- Re: [OpenAFS-devel] Re: O... Russ Allbery
- Re: [OpenAFS-devel] Re: O... Chas Williams
- Re: OpenAFS: conventions for new @sys?... Ken Hornstein
- Re: OpenAFS: conventions for new @sys?... R. Lindsay Todd
