How can I have multiple inkscape versions on the same machine (im on fedora8) and can you choose if those use the same or their own profiles?
Mihaela wrote:
How can I have multiple inkscape versions on the same machine (im on fedora8) and can you choose if those use the same or their own profiles?
All just guesses but...
1) Call them by different names or put them in different places. However if they use different versions of the same libs - well, that's up to you how messy you want to make you system.
I just checked my inkscape: $ inkscape --version Inkscape 0.45.1 (Mar 21 2007) $ ldd /usr/bin/inkscape | wc 76 301 4294 ...wow, inkscape is linking into about 76 different libs! Good luck at trying to support older versions!
2) Looks like inkscape puts personal perf stuff in the ~/.inkscape directory. Don't know if you can change that. If not, you can always create dummy user accounts and run a different version of inkscape in each.
...don't know if that helps you out or not, sorry.
stuart wrote:
Mihaela wrote:
How can I have multiple inkscape versions on the same machine (im on fedora8) and can you choose if those use the same or their own profiles?
All just guesses but...
- Call them by different names or put them in different places.
However if they use different versions of the same libs - well, that's up to you how messy you want to make you system.
I just checked my inkscape: $ inkscape --version Inkscape 0.45.1 (Mar 21 2007) $ ldd /usr/bin/inkscape | wc 76 301 4294 ...wow, inkscape is linking into about 76 different libs! Good luck at trying to support older versions!
The versions I want aren't so far apart, I want official 0.46 and a new dev build, maybe one more dev build if possible.
I tried compiling with "make" from a different folder (if I use make install everything will go in the official place and replace my current version right?) but some features are missing (i get warnings when running that version), I think it might be python related features.
What do you mean "call them by different names"?
Mihaela wrote:
stuart wrote:
Mihaela wrote:
How can I have multiple inkscape versions on the same machine (im on fedora8) and can you choose if those use the same or their own profiles?
All just guesses but...
- Call them by different names or put them in different places.
However if they use different versions of the same libs - well, that's up to you how messy you want to make you system.
I just checked my inkscape: $ inkscape --version Inkscape 0.45.1 (Mar 21 2007) $ ldd /usr/bin/inkscape | wc 76 301 4294 ...wow, inkscape is linking into about 76 different libs! Good luck at trying to support older versions!
The versions I want aren't so far apart, I want official 0.46 and a new dev build, maybe one more dev build if possible.
I tried compiling with "make" from a different folder (if I use make install everything will go in the official place and replace my current version right?) but some features are missing (i get warnings when running that version), I think it might be python related features.
What do you mean "call them by different names"?
I see... well, I'm only going to make suggestions. I don't build inkscape and it would probably take hours to go to somewhere like this: http://inkscape.modevia.com/svn-snap/?M=D to download, build and report back how exactly to build multiple versions - if it's possible.
The first thing you might try is to see if the inkscape tar'ed up source package uses "configure". If it does, and it is written well, there will probably be some options as to were the application can be installed. Pick something different for each version. Something like /usr/local/bin/inkscape_45/ and /usr/local/bin/inkscape_46/. Then to execute inkscape you would type /usr/local/bin/inkscape_45/inkscape or /usr/local/bin/inscape_46/inkscape. Remember, these are just off the wall suggestions (i.e. it's kind-of like getting a sheet of balsa wood and vague instructions on making a toy air plane).
Can anyone else help out?
B.T.W. If you are running fedora 8 did you know you should be able to install inkscape 0.46 binaries w/just 1 command:
yum install inkscape
On Fri, Jun 6, 2008 at 8:57 PM, Mihaela <myhaella5@...529...> wrote:
The versions I want aren't so far apart, I want official 0.46 and a new dev build, maybe one more dev build if possible.
Just compile any dev version and put the executable file anywhere you want, renaming it to some appropriate name. It will work with 0.46 files and prefs and vice versa. The worst you will get is some harmless warnings about unknown verbs or missing icons. In this way I have executables for all versions of Inkscape, and down to 0.40 they all work, although with more and more complaints as you go back in time. Only 0.39 and older can't run at all and crash - probably because they were compiled so long ago that the libraries have changed since.
On Sat, 2008-06-07 at 00:30 +0200, Mihaela wrote:
How can I have multiple inkscape versions on the same machine (im on fedora8) and can you choose if those use the same or their own profiles?
Probably the best way is to install them to a different prefix. For instance, I keep a stable version "installed" on my machine. To get a new dev version I do this:
$ vcs co http://blah/ inkscape $ cd inkscape $ ./autogen.sh $ mkdir build $ cd build $ ../configure --prefix=`pwd`/../install $ make install
You can then execute the dev version with:
$ <check out dir>/install/bin/inkscape
It will continue to use the same preferences files.
--Ted
Mihaela wrote:
Ted Gould wrote:
Im curious, what do autogen.sh and prefix='pwd' do? Is using vcs different from downloading source snapshots?
From the autogen.sh file: "This script does all the magic calls to automake/autoconf and friends that are needed to configure a cvs checkout."
I'm also wondering what prefix="pwd" does. I just use prefix=/home/user/.local, which works great for me, since I only keep the most recent version around - it should work for you, just switch to a different dir for each version.
Using SVN is nice because it updates very quickly - it only downloads the differences between your local repository and the main one. You just go to the directory and type "svn up", and a few seconds later (usually) you're ready to compile. You also don't really have to run autogen.sh and config each time (though sometimes you do).
JF
Hi all,
You don't really need to have multiple compiles to have different prefixes. Just build with binreloc. It doesn't need to be part of an autopackage to work. Basically, instead of looking for a static path for DATADIR, it dynamically looks relative to the executable for BR_DATADIR.
This is similar to how the win32 build can be located anywhere.
Look in prefix.h/cpp, and in path-prefix.h to see how to use it.
You will need to set the CFLAG #define ENABLE_BINRELOC 1 and probably #define BR_PTHREADS 1
bob
I'm also wondering what prefix="pwd" does. I just use prefix=/home/user/.local, which works great for me, since I only keep the most recent version around - it should work for you, just switch to a different dir for each version.
taking a guess here, i think the syntax would be
prefix=`pwd` (with backticks)
that way it will run the shell command 'pwd' (which conveniently returns your current working directory) and use the result to set the prefix.
so in a nutshell, it's just telling configure to use the current dir as a prefix. But mind that pwd should be enclosed in backticks (so that we get the command output), not single or double quotes.
hope i didn't get anything wrong here. ricardo
On Sun, 2008-06-15 at 23:13 +0200, Mihaela wrote:
- made a directory where I intend to keep all the dev versions, I
named it inkscape and put in /root/
This is unrelated to Inkscape, but please don't run as root. A lot of the security techniques used by Linux in general rely on the user being unprivileged. Being root breaks this assumption, and thus makes your system more vulnerable overall.
Im curious, what do autogen.sh and prefix='pwd' do? Is using vcs different from downloading source snapshots?
Basically it makes it so that the directory is relative to the directory that you're in. This is useful for me, as I tend to have pretty deep directory hierarchies and want everything to be together. It may not be as useful for other folks, but it does make the instructions generic to where ever you put your install.
--Ted
Ted Gould wrote:
This is unrelated to Inkscape, but please don't run as root. A lot of the security techniques used by Linux in general rely on the user being unprivileged. Being root breaks this assumption, and thus makes your system more vulnerable overall.
--Ted
I do login as a user, I'm not using the OS as root. But I often have to authorize root access to do the things I need to do. All my linux friends told me to go with user and they said I would only need to occasionally login as root until things settle down and I have all the features I need, but that hasn't happened yet and I still often have to use root access :p
I also ran into a weird problem recently (weird to a former windows user), my home directory became full (I think) and I couldn't save a file I was working on. Is there a limit on my home dir that is less than the available space on disc partition?
Mihaela wrote:
Ted Gould wrote:
This is unrelated to Inkscape, but please don't run as root. A lot of the security techniques used by Linux in general rely on the user being unprivileged. Being root breaks this assumption, and thus makes your system more vulnerable overall.
--TedI do login as a user, I'm not using the OS as root. But I often have to authorize root access to do the things I need to do. All my linux friends told me to go with user and they said I would only need to occasionally login as root until things settle down and I have all the features I need, but that hasn't happened yet and I still often have to use root access :p
I also ran into a weird problem recently (weird to a former windows user), my home directory became full (I think) and I couldn't save a file I was working on. Is there a limit on my home dir that is less than the available space on disc partition?
Assuming no quotas are in place, no, there is no practical size limit for home dirs. You may run "df" and "mount" in a console to check up on your disk usage.
On Wed, 2008-07-09 at 21:00 +0200, Mihaela wrote:
I'm using this method to compile (only from source snapshots) and I've just noticed that my dev builds can't import pdf files, while the official 0.46 can. How do I need to compile the dev builds to make sure all the features are included?
It's probably that you don't have the poppler development headers installed. On Ubuntu/Debian you can do this with:
$ apt-get build-dep inkscape
That will give you all the dependencies that were used to build the version of Inkscape that is distributed. You'll need to re-run configure after installing the headers.
--Ted
participants (8)
-
Bob Jamison -
bulia byak -
JonY -
Joshua Facemyer / Impressus Art -
Mihaela -
ricardo lafuente -
stuart -
Ted Gould