Summary: | New ebuild: x11-themes/gtk-css-engine dev-libs/libccss | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrey Ovcharov <sudormrfhalt> |
Component: | Current packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | gnome, jlec |
Priority: | Low | Keywords: | EBUILD, InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
libccss-9999.ebuild
gtk-css-engine-9999.ebuild |
Description
Andrey Ovcharov
2009-10-22 17:20:42 UTC
Created attachment 207915 [details]
libccss-9999.ebuild
dev-libs/libccss/libccss-9999.ebuild
Created attachment 207917 [details]
gtk-css-engine-9999.ebuild
x11-themes/gtk-css-engine/gtk-css-engine-9999.ebuild
@gnome Throw it back if your don't feel responsible for it. Best with a suggestion who probably wants it. Personally I prefer include a stable release or a development release... why ? - Because a release contains a "frozen" code - Because it's more stable - Because a day a live version can work/build... another day not - Because we can apply patches for a release (for a live version too, but that's more complicated) I see gtk-css-engine 0.3.1 on the timeline :) @herd: any remark ? * we want die clause on dodoc and other stuff like this * doing emake in src_configure is outright wrong, if you want a default src_compile, inherit base eclass * don't set keywords for untested arches * don't use autogen.sh, prefer eautoreconf and calls to appriopriate tools, it'll help you catch missing dependencies and changes to upstream autoconf * style: don't declare a local variable for one parameter to econf and USE ${PN} instead of "gtk-css-engine" (shorter) It looks like this project is dead, both at git.gnome.org and with informations found on ohloh. I think we can close this. |