Re: issues with using TARGET compilation argument

  • From: Liviu Andronic <landronimirc@xxxxxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Tue, 4 Dec 2012 11:38:32 +0100

On Tue, Dec 4, 2012 at 2:13 AM, Charles A Edwards <eslrahc@xxxxxxxxxxxxx> wrote:
>> stable release and latest trunk. For example, I would expect to have
>> installed:
>> /usr/local/bin/emelfm2-svn
>> /usr/local/share/pixmaps/emelfm2-svn
>> /usr/local/share/doc/emelfm2-svn
>> /usr/local/share/man/man1/emelfm2-svn.1
>
> Just curious.
>
> Is there a reason you do not wish to install svn to a different
> prefix?
>
To my understanding installing 'emelfm2' (release and SVN) in both
/usr and /usr/local (or whatever else) is not a viable solution.

What I am looking for is a trick that is used in LyX, where a
'./configure --with-version-suffix=-svn' call would:
- compile a 'lyx-svn' binary
- install all relevant files in */.lyx-svn or */lyx-svn directories and
- use a ~/.lyx-svn profile dir.
This allows seamless parallel installations of the stable and release versions.

I would like to achieve something similar with emel, as currently
whenever I want to test a fix/feature in trunk I have to uninstall the
release version. If I get this to work, I would look into setting up a
Launchpad PPA for daily emelFM2 builds, with the intent that the
release packages do not conflict with the development packages.

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: