> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] Im Auftrag von 
> Dejan Muhamedagic
> Gesendet: Dienstag, 5. Februar 2008 12:36
> An: General Linux-HA mailing list
> Betreff: Re: [Linux-HA] 32 / 64 Bit


Hi Dejan,


> 
> If I understand your question correctly, those libraries were
> moved to the $OCF_ROOT/resource.d/heartbeat/. OCF_ROOT is
> typically set to /usr/lib/ocf.
> 
> Does that help?


I understood the question the following way:
If someone develops a RA on his "development" platform he knows
the currently correct paths to the relevant components.
But if this developer thinks about making this RA runnable
on different architectures (32/64bit) or different platforms, he
doesn't know which parts (e.g. paths) are variable and architecture
or platform dependent.

So, shall the RA developer try to resolve paths at runtime using
defined and relyable environment variables? Where are they defined???

Or shall the RA developer send his implementation to you and you will
extract all absolute paths and replace them by build environment variables?

What is the right procedure?

Best regards
Andreas Mock

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to