Summary: | Inkscape-0.37 Ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marc Hildebrand (RETIRED) <zypher> |
Component: | New packages | Assignee: | Gentoo Graphics Project <graphics+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | charlie, gnome, pauldv, robmoss, troworld, tvon |
Priority: | High | Keywords: | EBUILD |
Version: | 1.4_rc4 | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.inkscape.org | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Ebuild inkscape 0.35
a refined inkscape-0.36 ebuild 0.37 ebuild |
Description
Marc Hildebrand (RETIRED)
![]() Created attachment 20688 [details]
Ebuild inkscape 0.35
Need an update. 0.35 will be out very soon and theres nothing in portage yet at all. a few comments : * the description isn't really a description ('seeks to be' ?) * keywords should always start out ~arch * ebuild should use gnome2 eclass * dunno why the MY_P trick is used, seems unneeded * depend probably needs fixing (i know this misses elements for sure) * config switches only switch one way : bad * dunno about static compile, i never enable that with useflags -> you could use it on almost any ebuild, could probably better be set via cflags, i'd say ditch it and last but not least, inkscape is afaik atm pretty much exactly sodipodi : in that sense it's not very useful having them both at this time. It's a new project, let it mature first. I'd disagree with you there foser. Inkscape is moving in a radically different direction with it's goals, features, UI, and codebase. We should drop in an ebuild for the upcoming 0.36 release which will be markedly different from Sodipodi. Inkscape 0.36 is out: http://www.gnomedesktop.org/article.php?sid=1521 There's now a significant difference between Sodipodi and Inkscape. Hmmm, I don't agree with all your points foser, but of course I'll check the ebuild as soon as I have time to, which will be at the weekend. As I stated above this ebuild is not perfect. If someone feels the urge to take it, go right ahead, I have enough stuff to maintain. Cheers, Marc. Created attachment 22034 [details]
a refined inkscape-0.36 ebuild
This inkscape build is very heavily influenced by the latest sodipodi (0.33)
ebuild. Hopefully it meets Gentoo's standards better.
*** Bug 35608 has been marked as a duplicate of this bug. *** That ebuild works a treat for me. Apart from sourceforge mirror issues, the ebuild works fine here too. Inkscape is a must.. Sodpodi is falling behind and Inkscape is only improving and quickly too. Given the fact that Inkscape 0.37 is almost out, perhaps the 0.36 ebuild could be unmasked? Anyone out there? Inkscape 0.37 is now out. Created attachment 25521 [details]
0.37 ebuild
Hi!
Please test this one.
Cheers,
Marc.
WORKSFORME! As an ebuild for Inkscape 0.37 has just been submitted to breakmygentoo.net's Bugzilla, I feel obliged to ask a question - is there any reason as to why 0.37 isn't in portage? Is it still too immature? If so, I'll stick it on breakmygentoo, but if not then I'll wait for it to show up in portage. Heh, I was just coming here to submit my 0.37 ebuild... guess someone beat me to it :) Just for your information, that 0.37 ebuild doesn't need >=dev-libs/libsigc++-1.2.5 You can replace the line with >=dev-libs/libsigc++-1.2 We've had a production-quality ebuild available here for over 5 (FIVE) weeks now... is there any reason as to why this isn't in portage? I know what the policies are, but I don't think that Inkscape contravenes any of them; IMHO it's sufficiently mature. I would put it there myself, but I'm not a developer, so I can't help :-( in cvs. atk is not defined in the pack, not needed to be in the deps. Same for pango. Use lowest common denominator for libsigc -> 1.2 , not 1.2.5 . There doesn't seem to be a dep on librsvg anymore. Intltool dep needs to be upped to 0.29 for XML-Parser to be covered (ok, i don't expect you to know that one). There is no gnome switch, the switch & deps as they are are useless. There are no mlview or kde switches, why are they in the ebuild ? You put 4 arches in KEYWORDS, you can only put arches in on a new pack you have actually tested or a reporter has tested. This should be ~x86 only. The license of the code is not just GPL anymore, you should check. You miss to install quite a few docs, but those are minor issues. In short zypher, do you even check the ebuild before you put it in? You should, it's your responsibility. Ok, I fixed the ebuild. (yes, I had checked it) Actually the instructions included in the release are a bit outdated regarding deps and flags. Should have checked that. Hope the new ebuild satisfies qa more. As for the docs I'll have a closer look at that. Please check, comments welcome. From everyone ;) Cheers, Marc. Licenses still not correct (?) You removed the mmx switch, afaics it is functional so it shouldn't have been removed. You removed the mmx switch, but mmx is still in IUSE. You removed the gnome switch, but left the conditional deps in. Bad. You probably want the switch, because it's useful. It just didn't work with the former ebuild, because the switch got renamed. Added complication is that 'gnome' for gnome-print capabilities is probably not the right flag to use. Yep, you're right. I implemented the flags again. The gnome use-flag is the only one I can think about when wanting gnome-print. A local flag seems a bit useless, who would use +gnome-print -gnome anyway? The licenses are ok (just take a look at the libsigc++ ebuild for example). Well, maybe you just don't need/want gnome-print stuff, but do want gnome. It's not about you, but what is reasonable to request. About the licenses once again, afaics you still define the wrong license. |