On May 7, 2009, at 9:15 AM, Mark Hatle wrote:

> I like the idea of changing the locations to be loaded into macros.   
> This helps my relocatable RPM mechanism.. ;)
>

Using a macro for the path doesn't tell me what I asked:

	Where should per-interpreter initialization and
	private JS extensions be installed?

> My only concern is how do we deal with working with roots or not?   
> In my case, I doubt I ever want to load interpreters from inside of  
> a chroot, however I think I can fairly easily see a need for doing  
> that within an installer framework.
>

If the stuff isn't installed (because no path has been chosen),
then its impossible to consider using the "stuff" outside
of a rpm build tree.

> Perhaps what is needed is a macro, convention, etc that indicates  
> either to perform the chroot before the load.. or contains the path  
> of the chroot for use within a macro  %{nil} if not set?  (Just  
> thinking out loud of how I can use this for the cross-architecture  
> installs..)
>

I need answers for what path, not how to "Have it your own way!" using
macros.

73 de Jeff