On 02/18/09 20:20, Bart Smaalders wrote:
jan damborsky 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.
Right now we publish separately on each architecture, and then merge the
results. This means that files that are not common to all architectures
are tagged; files that are common to all are not.
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'.
Any file that doesn't have a variant.arch tag is architecture
independent.
Adding tags to all directories, dependencies, text files, etc, to
say "independent" seems somewhat useless to me.
I see - thank you for clarifying this. Just to summarize if I got
it correctly:
* 'platform independent' action (like text file) doesn't have
variant.arch tag
* action which is not necessarily platform independent, but is found
the be common for both Sparc and x86 during merge process doesn't have
variant.arch tag
* Are there actions where variant.arch is set for multiple architectures
(Sparc and x86) ?
Thank you,
Jan
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
