On 02/18/09 17:17, Shawn Walker wrote:
jan damborsky wrote:
On 02/17/09 22:30, Brock Pytlik wrote:
I'm not sure we have a notion of "platform independent". We have a
notion of "found on sparc and x86".
I feel those two cases are a little bit different. 'platform
independent' means that
the same file works across all supported and potentially new platforms
without need to accommodate it, e.g. recompile. Those might be for
instance
non-executable text files.
On the other hand, 'found on Sparc and x86' means that you have separate
files for each platform - in our case one for Sparc, one for x86.
Not true; a single file action can have variants for multiple
architectures.
I agree - I should have expressed myself more cleanly.
What I meant to say is that unlike 'platform independent'
single file actions where one might serve all architectures,
'platform dependent' ones have to define one action for each
architecture. Is my understanding correct ?
I'll let Bart or someone else clarify if I've gotten that wrong. You
will be able to search for packages which have x86 and Sparc actions
within them (though currently there's no plan to enable a search
saying, "all actions within these packages must contain x86 and
Sparc variants")
I think that having support for 'platform independent' might make
this kind of operations easier as it provides you with additional
information, since even if all actions supports both platforms, it
wouldn't necessarily mean that those actions are 'platform independent'.
We've discussed the "platform independent" vs. specifying the
supported, tested architectures. The conclusion was that specifying
the specific, supported architectures of your package was the
preferred method.
I see - thanks for clarifying this,
Jan
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
