Hello,
Say we put a library into Userland and we build it as-is from the source
archive available from the community. Then imagine sometime later we
want to optimize some routines in it especially for our own benefit -
but for some reason the community does not want those optimizations.
I see two possible scenarios unfolding from this:
1) community doesn't take our optimizations, our build of that
component now diverges some amount from the publicly available version
and we just build/package what we have with our optimizations and anyone
that installs that package gets our optimizations - for better or worse.
2) if (for whatever reason) the optimized library works good for us but
in general isn't the best one for most folks to use: we maintain 2
different versions of the library, one with optimizations and one
without and we build/package both of them
Scenario 1 is easy (except for the fact that it may make upgrades a real
pain to merge in/re-code our optimizations.) But can we deal with
scenario 2 somehow in Userland? I know we've talked about having
multiple versions of other components where one lives as the default and
the other (newer or older) is made available as a choice, but can that
be done with a library? I think with multiple versions of a component
(i.e. Python) theres something specific in the path that indicates which
version you run. I don't know if libraries have another way to deal
with this?
This is just a hypothetical question and I might be worrying for
nothing, however I want to know if I can deal with scenario 2 if it
occurs. Unless there's another way to handle such a problem?
Thanks,
Kevin.
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
