Re: issues with using TARGET compilation argument
- From: Liviu Andronic <landronimirc@xxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Tue, 4 Dec 2012 17:07:28 +0100
On Tue, Dec 4, 2012 at 1:02 PM, Charles A Edwards <eslrahc@xxxxxxxxxxxxx> wrote:
>> To my understanding installing 'emelfm2' (release and SVN) in both
>> /usr and /usr/local (or whatever else) is not a viable solution.
>
> The only issue is that whichever is listed 1st in Path
> will be invoked Unless you use the full path when invoking
> /usr/bin/emelfm2, /usr/local/emelfm2 /whatever/emelfm2 etc.
>
Yes, from a maintainer's POV this is a bit problematic.
> Just for fun last night I built an rpm for emelfm2 using
>
> prefix=/home/charles/emelfm2-svn
> and for post/postun I used
>
> %post
> ln -s /home/charles/emelfm2-svn/bin/emelfm2 /usr/bin/emelfm2-svn
>
> %postun
> rm -f /usr/bin/emelfm2-svn
>
> If I invoke with emelfm2 my /usr/bin install is launched if I
> invoke with emelfm2-svn my /home/charles install is launched.
> I can launch/run either/both without issue.
>
Interesting. But do both instances use the same profile: 'charles'? I
would like the release and development versions to use independent
configs, and it seems to me that in this setup it is not the case.
Liviu
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
Other related posts:
