- Inkscape Devel - Inkscape Mailman

inkscape root dir tidying thoughts
by Bryce Harrington 15 Aug '17

15 Aug '17

With the cmake and git conversions complete, and autotools and bzr bits removed, I am wondering if there's some additional cleanup of stuff accumulated in our repository's root directory. But much of this I'm not 100% sure about (and that maybe why others haven't already dealt with it). ------------------------------------------------------------------------ + distro + libgc.supp + tools-version.sh I think these may be obsolete. They've been in the codebase forever, but I don't know what they are used for anymore. I'm guessing they're autotools leftovers; can we drop them? ------------------------------------------------------------------------ + inkscape.ico + inkscape.png The share/icons/application/ directory is the formal place for our icons, with share/branding/ the official source for branding files. Only the windows packaging refers to inkscape.ico. So I think this could be moved to packaging/. Or perhaps windows could be changed to use the .png files like everything else? Doxyfile seems to reference inkscape.png but I believe it could as easily use one of the icons in share/icons/application/, but see below... ------------------------------------------------------------------------ + Doxyfile This doxygen config file works fine (just ran it). However according to http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation we aren't posting doxygen pages online any more. In any case, doxygen lets you pass the config file name on its command line, so no reason this has to live in the root directory. Unless anyone has strong feelings otherwise I propose moving this file to doc/ with our other code/architecture docs. Or... other ideas? ------------------------------------------------------------------------ + inkscape.spec.in This is an old RPM build file I made way way back. I'm sure Fedora has something better, and besides this is _completely_ out of date. I will be deleting it. ------------------------------------------------------------------------ + inkscape.desktop.in + inkscape.desktop.template Is inkscape.desktop.in generated from inkscape.desktop.template? Do we need both files? ------------------------------------------------------------------------ + mingwenv.bat + mingwenv.cmake + msys2checkdeps.py + msys2installdeps.sh + msysenv.sh + inkscape.appdata.xml.in + Info.plist.in + appveyor.sh + appveyor.yml + .gitlab-ci.yml + .snapcraft.yaml + packaging/ I know a lot of tools expect config files in the project's root directory, but can any of these be moved to packaging/? (Or maybe a utils/ dir?) Several of these have description snippets that are essentially the first few paragraphs of the README. If the README is revised (see below), it may be worthwhile to resync the text in these from that. ------------------------------------------------------------------------ + download-gtest.sh This still seems necessary for setting up gtest (although current trunk breaks on configure due to lack of a "Findgtest.cmake"; but that seems unrelated). Having to use this script has always seemed a bit hacky to me. (and it's downloading gtest 1.7, but 1.8 is current). I know there's been some good work done on improving our testing cmake rules, I wonder if there is a way we can eliminate this script? ------------------------------------------------------------------------ + testfiles/ Speaking of tests... Is there a reason why we call this directory testfiles/ rather than a more traditional name like 'test/' or 'tests/'? ------------------------------------------------------------------------ + INSTALL The installation directions here are for autotools so the whole file is obsolete. I only hesistate to delete it because I believe `make distcheck` requires it. So question here is should we move the installation directions currently in the README.md file to INSTALL? ------------------------------------------------------------------------ + README.md + README.ca.txt + README.de.txt + README.es.txt + README.fr.txt + README.it.txt + README.pt_BR.txt + README.sk.txt + README.sr.txt Speaking of the README, we've had these translations of the README for a long, long time. Most have not been updated to reflect the autotools -> cmake move, some haven't been updated in a decade. None have followed the main README's reformatting to markdown. But I wonder if translations of the README are that necessary? If not, would anyone be troubled if we dropped them at this point? Aside from the installation directions (which are out of date anyway, and maybe should move to INSTALL), the information in the README is just introductory stuff that exists in translated form on our website and elsewhere so The first section of the README we have used far and wide all over the place. It's a stock text we cut and paste into anything that needs a description of our project. But it's been pointed out to me that this doesn't really reflect the current state of Inkscape and all the stuff that's been achieved since it was written. So, we may want to consider revising this. Does anyone know of a more current description of Inkscape that we could leverage for this? ------------------------------------------------------------------------ + inkscape.pod + inkscape.de.pod + inkscape.el.pod + inkscape.fr.pod + inkscape.ja.pod + inkscape.sk.pod + inkscape.zh_TW.pod + inkview.1.in + man/ Unlike the README's, the translated man pages have been getting updates. The --no-convert-text-baseline-spacing option is only documented in the English inkscape.pod, but the previously added option, --export-ps-level, (from 2013) is present in all. However, these should move down into the man directory. The CMake code is already in CMakeLists.txt to generate the .pod files from the man/ directory, so recent changes to the root *.pod's just need to be sync'd with the corresponding files in man/ and then removed. As an aside, I know we eliminated Perl from the build system, but it's still used for the man page generation (the 'p' in pod stands for perl). I like the POD format, but raw man page syntax (TROFF) isn't *that* complicated; if we wanted, we could just keep all the man pages as troff, eliminate pod usage, and simplify our build requirements. (Compare inkview.1.in with man/inkview.pod.in to see the difference). Would anyone be opposed (or favorable) to this change? ------------------------------------------------------------------------ + fix-roff-punct + utf8-to-roff These perl scripts were used to fix up punctuation goofs by pod2man. If we moved away from POD, then these are entirely superfluous and can be dropped. -------------- + COPYING + GPL2.txt + GPL3.txt + LGPL2.1.txt Next, licenses... As detailed in the COPYING file, the only reason we have GPL3.txt is because there's a few files in our tree copied from GIMP. Could someone please take the task of eliminating those files, so Inkscape can return to being pure GPL2? The LGPL2.1 isn't a problem, but according to COPYING it's only there due to some libs we copied into the tree (I see libavoid is LGPL, is there anything else?) If the LGPL libs were changed to be external dependencies instead of copied into src, we could eliminate the LGPL2.1.txt file too. ------------------------------------------------------------------------ + CMakeLists.txt + CMakeScripts/ + cmake_uninstall.cmake.in + config.h.cmake CMake is nice and concise compared to autotools. I do wonder if cmake_uninstall.cmake.in could perhaps be moved into CMakeScripts/. If anyone else wants to move it, please do, else I'll look into it some time. ------------------------------------------------------------------------ + astylerc This config file appears to be for a code formatting tool. I vaguely remember kk discussing it a while back. Is anyone still using it? The astyle man page indicates it supports using --options=FILENAME to specify a path to astylerc, so the file could be moved to utils/ or elsewhere. I see we already have the options documented at https://inkscape.org/en/develop/coding-style/ including directions for how to store the settings locally in ~/.astylerc. If no one is actively using this tool, that might be a better solution and remove astylerc from the codebase. ------------------------------------------------------------------------ + _clang-format I'm not sure why this is in the tree. Guessing it was a jenkins-related thing? I suspect we can drop this. ------------------------------------------------------------------------ + setup/ This appears to be current, but what is it? It has a single subdir with a single file, which looks like a copy of inkscape.desktop.in with translations embedded. Why is this in a directory called 'setup'? ------------------------------------------------------------------------ + ChangeLog With the newest entry in this file being from 2014, this looks vestigal. I think it used to be needed for packaging, and I think it dates to pre-bzr. Anyone know if there's a reason to keep it? ------------------------------------------------------------------------ + AUTHORS + TRANSLATORS + NEWS + doc/ + share/ + src/ + po/ This is all pretty stock, no comment here. Bryce P.S. if you've read to this far, thanks! This ended up way longer than I anticipated, sorry!

13 35

Correct download URL for source ?
by Ken Moffat 13 Aug '17

13 Aug '17

When I downloaded 0.92.2 using firefox, I thought that the link was to https://inkscape.org/en/release/0.92.2/source/archive/dl/bz2/ (but I might have misread the tiny text), and presumably it had inkscape-0.92.2.tar.bz2 on the end of it. But now that I try to go there directly I get inkscape's Page Not Found, and using that to search for inkscape-0.92.2.tar.bz2 fails. I see that Arch seem to be using https://media.inkscape.org/dl/resources/file/inkscape-0.92.2.tar.bz2 but that too fails for me with 404, or 403 for the directories above that. So, please, where should I point people to so that they can download it with a browser or wget ? ĸen -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment

2 2

Rerun Cakke
by Jabier Arraiza 12 Aug '17

12 Aug '17

Hi all. Please I just push a minor improvement and if you have compiling isues with a icon, please re-run cmake. (not need to remove cache cmake file). Sorry for the inconveniences, Jabier.

1 0

Icon names
by Alex Valavanis 12 Aug '17

12 Aug '17

Hi Tav, Is there any chance you could use your icon-extracting Perl script to generate a list of Inkscape's icon-name strings? It would be good to put a table of names/descriptions on the Wiki to help people develop custom icon themes. AV

2 1

Download Page Redirect Issue?
by Ryan Gorley 11 Aug '17

11 Aug '17

Can someone confirm that they're having similar behaviors: When I visit inkscape.org I am properly assigned my language (/en/), when I hover over the download link it shows the proper URL (https://inkscape.org/en/release/), but when I click the link I am redirected to the French language version of the page (https://inkscape.org/fr/release/0.92.2/). I've tested in three browsers, it's not a local caching issue as far as I can tell. Seems like a serverside page caching issue to me, or maybe a simple redirect typo. Just want to see if I'm the only one.

6 7

Can not open .eps files
by Marc Alexander Gross 11 Aug '17

11 Aug '17

Hi, I installed today Inkscape. Unfortunately I could not open any .eps files. Neither if I open a jpg and translate it into EPS and safe it in EPS formate. Please could you help me out, to solve this problem? Regards Marc

3 5

Please update 0.93 release notes
by Bryce Harrington 11 Aug '17

11 Aug '17

Everyone working on trunk, please take a few minutes to jot down what you've been working on: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.93 Also, if there's changes others have done that you're aware of, please add those too. Even placeholder text would help indicate where further fleshing out is needed. Thanks, Bryce

1 0

Fwd: Re: Debian 8 compatibility falling apart after one month of Debian 9
by Michael Soegtrop 11 Aug '17

11 Aug '17

Dear Eduard, dear Inkscape Team > If this version matches the actual requirement unexpected build failures > like Michael was experiencing should be impossible as cmake would > already warn at the configure stage. I would think that CMake allows newer versions than the specified one, unless explicitly told otherwise. The issue here is that some GTK 3.16 are actually used although only GTK 3.8 features should be used (as far as I understood). I have some experience with creating build systems which use specific package versions based on Cygwin. Since there is a working MSys build, it shouldn't be difficult to build with specific package versions - one just has to create a local cygwin or MSys package repository, which keeps these specific versions and tell the Cygwin/MSys installer to use that one. The Cygwin installer creates a suitable repository as a cache automatically. Not sure how this works with MSys, but I guess it has similar features. The main issue here might be to get the versions mentioned in the Wiki. One might have to build them from scratch. If someone has a years old cache folder of Cygwin or MSys with all the old package versions, please put is somewhere. It would make sense to run two builds, one with the latest packages and one with an archived set of packages. Best regards, Michael .

6 16

Organic Funding
by Martin Owens 10 Aug '17

10 Aug '17

Dear developers, We've just concluded our board meeting and one of the issues was funding. We're kicking around an idea of allowing some developers to use the service Patreon (http://patreon.com/) to collect subscriptions to fund their Inkscape development. This system of funding would be quite different from either a centralised funding model or the status quo of non-user involvement. These are some very raw thoughts for considering and I'd love to get more feedback from the wider developer community: * Developers would be allowed to create a Patreon page which describes their work on Inkscape. * Each developer would be shaping their focuses and would be responsible to keeping their Patreon pages up to date. * Developers may only define themselves as Inkscape developers on patreon if: . + They are Inkscape developers (in the list of devs) . + Are considered active in the project. . + Present Inkscape in a good light on their pages. . + Have asked for permission from the developers list. * Developers would be removed from the scheme by the developers if . + They are not active in the project for 2 months . + Are involved in an conduct infraction which gets them removed from the project. * People claiming to be Inkscape developers without permission will be considered to be using the Inkscape trademark inappropriately. (must check legal with Conservancy to make sure this is true) * The Inkscape general fund continues to be the donation headline, money going towards hackfests and other resources for the project. * The project would do periodic funding drives to improve donations and subscriptions to our patreon developers. Using social media and news announcements to improve funding. * Contributors to patreon developers would NOT receive sponsorship rewards from Inkscape (i.e. sponsorship levels on the website). * Patreon developers would continue to get sponsorship for hackfest expenses much like any other developer would. == Status == We have two developers who are prepared to trial such a system. Tav and Mc (Marc), both attended the hackfest, both have worked on Inkscape intensively for quite a while. I want to see if it's possible try and get a trial set up quickly. Mc will leave education in 2 months and must decide to continue developing Inkscape or move on to full time employment. Best Regards, Martin Owens

10 20

Thanks making 0.92.2 happen
by Ryan Gorley 10 Aug '17

10 Aug '17

The new release is available for download on the slick new release page <https://inkscape.org/en/release/0.92.2/>, the announcement <https://inkscape.org/en/news/2017/08/07/inkscape-0-92-2-release-announcemen…> is up, and we're in the midst of letting the world know <https://gitlab.com/inkscape/inkscape-vectors/press/issues/1>. From my vantage point it was really awesome to see /many/ of you step up to pull this all together--often during busy schedules and into the early mornings. I just wanted to say wow, and thank you! -- Ryan Gorley // Dijt <https://dijt.co> // Managing Partner

4 4