adding an environment variable for everyone

For our product, we require an environment variable be set. The easiest way
we’ve found to do this is to add an export to /etc/profile. But this of
course very clunky. Is there any other way of doing this? Like, some magic
directory that gets searched for files of a certain name specification, then
run automagically? I seem to remember seeing some rc scripts, or scripts
that ran rc scripts, doing something like this …

Also, is there any way to augment the contents of the
/usr/photon/plugins/config file automagically? Seems like you could do
something like perhaps you could allow subdirectories under the plugin
directories corresponding to the MIME type and/or file extension (link them
together). These directories could contain the per-plugin contents of the
config file …

Patrick Mueller
Patrick_Mueller@oti.com

For our product, we require an environment variable be set. The easiest
way
we’ve found to do this is to add an export to /etc/profile. But this of
course very clunky. Is there any other way of doing this? Like, some
magic
directory that gets searched for files of a certain name specification,
then
run automagically? I seem to remember seeing some rc scripts, or scripts
that ran rc scripts, doing something like this …

Also, is there any way to augment the contents of the
/usr/photon/plugins/config file automagically? Seems like you could do
something like perhaps you could allow subdirectories under the plugin
directories corresponding to the MIME type and/or file extension (link
them
together). These directories could contain the per-plugin contents of the
config file …

I wrote a plugin intaller and uninstaller for the image plugin I wrote. It
is very specific at the moment but
it could be made more generic. It uses the PxConfig functions. It is called
automatically when the package
is installed and uninstalled.

Very cool. Thanks for the tip. … 'course, it would still be handy to
have each plugin’s config in a separate file/directory …

Patrick Mueller
Patrick_Mueller@oti.com



Jerry Kirk <Jerry.Kirk@Nexwarecorp.com> wrote in message
news:90lv4r$agd$1@inn.qnx.com

For our product, we require an environment variable be set. The easiest
way
we’ve found to do this is to add an export to /etc/profile. But this of
course very clunky. Is there any other way of doing this? Like, some
magic
directory that gets searched for files of a certain name specification,
then
run automagically? I seem to remember seeing some rc scripts, or
scripts
that ran rc scripts, doing something like this …

Also, is there any way to augment the contents of the
/usr/photon/plugins/config file automagically? Seems like you could do
something like perhaps you could allow subdirectories under the plugin
directories corresponding to the MIME type and/or file extension (link
them
together). These directories could contain the per-plugin contents of
the
config file …

I wrote a plugin intaller and uninstaller for the image plugin I wrote.
It
is very specific at the moment but
it could be made more generic. It uses the PxConfig functions. It is
called
automatically when the package
is installed and uninstalled.