| Summary: | New ebuild: wxifm-1.0.3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andreas Thillosen <corrosifdev> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | wxwidgets |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://ifm.sourceforge.net/ | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
wxifm-1.0.3.ebuild
wxifm-1.0.3.ebuild wxifm-1.0.3.ebuild wxifm-1.0.3.ebuild wxifm-1.0.3.ebuild |
||
|
Description
Andreas Thillosen
2005-08-06 03:00:39 UTC
Created attachment 65217 [details]
wxifm-1.0.3.ebuild
New ebuild for wxIFM, a docking library for wxWidgets.
I suggest to put it in x11-libs.
Please fix the following and reopen:
* Are those KEYWORDS really correct?
* You need an unzip DEPEND.
* You can use ${PN}, ${PV} etc in SRC_URI
* I think your S= is wrong, based upon the copying you're doing.
* ${S} needs quoting.
Created attachment 66788 [details]
wxifm-1.0.3.ebuild
- Package was tested only on x86, so just leave one KEYWORD "~x86".
- emake instead of make in src_compile.
- removed dodoc license file.
- make use of ${MY_P} variable for more flexibility.
- added SLOT="0".
- added an unzip dependency.
I think my S= is right, as it is used only in src_install, and it picks the .a
libs at the right place.
Thanks for the tips...
By the way, what do you mean by "${S} needs quoting."?
In the official gentoo documentation, I don't find such a recommandation, and
many official ebuilds don't use this.
Created attachment 66791 [details]
wxifm-1.0.3.ebuild
In "die" case, talk about emake rather than make.
For variables which might contain spaces, such as ${S} and ${D}, it's best to
quote them. As it stands, a lot of ebuilds will break if you set any of the
portage paths to something containing a space. However, we're sloooowly working
towards making the tree space-safe, and fixing things going in is an easy way to
start.
Created attachment 66805 [details]
wxifm-1.0.3.ebuild
Use quotes with variables.
Created attachment 66806 [details]
wxifm-1.0.3.ebuild
Whoops, quotes don't work everywhere :)
You forgot to reopen. Upstream of this project seems very much dead. To begin with, development of wxIFM 1.0 ceased back in 2006 upon reaching version 1.0.5. The project then morphed into theoretically GUI-toolkit-agnostic IFM 2.0, which however has never made it out of alpha and hasn't seen any repository activity since 2009. Is there still any user demand for adding IFM to Portage? I won't be adding a dead project to the tree even if there is demand for it. |
