Re: [Inkscape-devel] Official Inkscape PPAs
Hi. Thanks for setting the PPA! Is it possible to change the name of that builds from inkscape to something like "inkscape-devel" so it doesn't replace the stable build from repos? Inkscape is one of the main tools in my pipe and I give it a heavy daily use, so I cannot afford to have an unstable inkscape, but I don't want it to keep me from testing the new stuff! Being able to install both versions would solve the problem.
Thanks in advance Gez.
I already got info from Ted about this issue and will be forwarding on what I got to Alex tomorrow when at the computer.
Cheers, Josh
P.S. FYI, we always try to keep trunk as stable as possible and still useable for production work... no guarantees though. ;-) On Jun 13, 2011 10:03 PM, "gespertino@...400..." <gespertino@...400...> wrote:
Hi. Thanks for setting the PPA! Is it possible to change the name of that builds from inkscape to something like "inkscape-devel" so it doesn't replace the stable build from repos? Inkscape is one of the main tools in my pipe and I give it a heavy daily use, so I cannot afford to have an unstable inkscape, but I don't want it to keep me from testing the new stuff! Being able to install both versions would solve the problem.
Thanks in advance Gez.
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Looks like there is a problem with the version number, specifically APT considers it lower than the version currently in Natty (0.48.1-2.1ubuntu1).
@Krzysztof - Yes, I thought this could be an issue. I chose "inkscape_0.48+devel+..." as it is the version we set for trunk in configure.ac. This means that apt will upgrade "inkscape_0.48" package versions but not "inkscape_0.48.1".
I guess the problem here is... do we actually consider inkscape trunk to be a "higher" version than the inkscape 0.48.1 release? As I see it, 0.48.1 and trunk are actually *different* options (in different branches) for upgrading 0.48, rather than there being a strict 0.48+devel > 0.48.1 > 0.48 order. In other words, I guess it's technically possible for 0.48.1 to contain more fixes than trunk.
Anyway, semantics aside... if we decide that we want the daily-build package to always be the highest version, we can't use "inkscape_0.48+devel". We could use "inkscape_0.49~devel" instead but this could cause problems in the future because we don't know for sure that we'll call the next release 0.49 yet.
Is it possible to change the name of that builds from inkscape to something like "inkscape-devel" so it doesn't replace the stable build from repos?
@Gez - Perhaps this is the best solution. Separating the stable and devel packages would work best semantically, I think. i.e. the user can have both "inkscape-devel_0.48+devel..." and "inkscape_0.48.1..." packages installed at once.
I already got info from Ted about this issue and will be forwarding on what I got to Alex tomorrow when at the computer.
@Josh - Yes, please send it on!
AV
On 14 June 2011 06:06, Josh Andler <scislac@...400...> wrote:
I already got info from Ted about this issue and will be forwarding on what I got to Alex tomorrow when at the computer.
Cheers, Josh
P.S. FYI, we always try to keep trunk as stable as possible and still useable for production work... no guarantees though. ;-)
On Jun 13, 2011 10:03 PM, "gespertino@...400..." <gespertino@...400...> wrote:
Hi. Thanks for setting the PPA! Is it possible to change the name of that builds from inkscape to something like "inkscape-devel" so it doesn't replace the stable build from repos? Inkscape is one of the main tools in my pipe and I give it a heavy daily use, so I cannot afford to have an unstable inkscape, but I don't want it to keep me from testing the new stuff! Being able to install both versions would solve the problem.
Thanks in advance Gez.
EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Tue, Jun 14, 2011 at 3:38 AM, Alex Valavanis <valavanisalex@...400...> wrote:
Is it possible to change the name of that builds from inkscape to something like "inkscape-devel" so it doesn't replace the stable build from repos?
@Gez - Perhaps this is the best solution. Separating the stable and devel packages would work best semantically, I think. i.e. the user can have both "inkscape-devel_0.48+devel..." and "inkscape_0.48.1..." packages installed at once.
Speaking of semantics, I would generally expect a package named 'inkscape-devel' to provide source/header files for building against. I'd prefer it were named something like 'inkscape-daily' or 'inkscape-trunk'.
0.02, Chris
Yes, that sounds better! My preference is probably inkscape-daily.
AV
On 14 June 2011 16:39, Chris Mohler <cr33dog@...400...> wrote:
On Tue, Jun 14, 2011 at 3:38 AM, Alex Valavanis <valavanisalex@...400...> wrote:
Is it possible to change the name of that builds from inkscape to something like "inkscape-devel" so it doesn't replace the stable build from repos?
@Gez - Perhaps this is the best solution. Separating the stable and devel packages would work best semantically, I think. i.e. the user can have both "inkscape-devel_0.48+devel..." and "inkscape_0.48.1..." packages installed at once.
Speaking of semantics, I would generally expect a package named 'inkscape-devel' to provide source/header files for building against. I'd prefer it were named something like 'inkscape-daily' or 'inkscape-trunk'.
0.02, Chris
On Tue, 2011-06-14 at 10:39 -0500, Chris Mohler wrote:
Speaking of semantics, I would generally expect a package named 'inkscape-devel' to provide source/header files for building against. I'd prefer it were named something like 'inkscape-daily' or 'inkscape-trunk'.
No imagination in that naming scheme. How about:
inkscape-blot (you know for cleaning up messing excesses that could lead to horrible smudging if we let them through?)
Martin,
On Tue, 2011-06-14 at 10:39 -0500, Chris Mohler wrote:
Speaking of semantics, I would generally expect a package named 'inkscape-devel' to provide source/header files for building against.
Oh, that's true. I didn't think about -dev files. Good point.
I think -daily would be fine, but if it is really a daily build. Otoh, -trunk is the way scribus is already naming dailies in their PPA, so probably is more newbie friendly if that's unified in libre graphics packages.
2011/6/14 gespertino@...400... <gespertino@...400...>:
I think -daily would be fine, but if it is really a daily build. Otoh, -trunk is the way scribus is already naming dailies in their PPA, so probably is more newbie friendly if that's unified in libre graphics packages.
I would go for "inkscape-trunk", because I think the build frequency should not be in the package name (and the name doesn't make it clear what exactly is built daily). Regards, Krzysztof
participants (6)
-
Alex Valavanis
-
Chris Mohler
-
gespertino@...400...
-
Josh Andler
-
Krzysztof Kosiński
-
Martin Owens