On 5/11/06, ted@...11... <ted@...11...> wrote:
On Wed, 10 May 2006, bulia byak wrote:
- Designate this as a mustfix bug for the release: Inkscape must
always use its own python, not something in PATH. Certainly I'm not the only one with Python installed on Windows, so this issue is bound to happen to other people.
Is there ever a reason that you'd want to use the version in the PATH? It seems atleast for testing you might want to use a different version.
If you want to test how some changes affect it, just make those changes to Inkscape's python and test. Or make inkscape/share/python a symlink/batch file calling the "real python". Anyway, I don't think we need to add an option for that.
- Enable extensions/effects by default and remove the prefs setting.
I don't know of anything that prevents us from doing that.
I agree. I think we should make the "configurable menu" the whiteboard menu and make it compile in by default. Thoughts?
Last I heard, it even gets compiled in the Windows version. If it also works :) let's just enable it always.
In Linux binaries we provide, I think it should also be enabled, and the library it uses linked statically. Is this possible?
While I have no problem building releases, I have issues with consistent net access right now -- so it would be hard for me to upload them. (hopefully the bcm43xx driver in 2.6.17 will solve this, Bryce can you go kick Linus and get him to release it?) This is why all of my checkins have been 'batches' and why I'm rarely in the chat room. While I enjoy the task, someone else should probably be the 'release builder' for this revision.
So we need a tarball king :) Volunteers welcome!