Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 148256 - vdr-skincurses bound to APIVERSION
Summary: vdr-skincurses bound to APIVERSION
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo VDR Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-19 15:17 UTC by Lucian Muresan
Modified: 2006-09-21 06:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
adapts vdr-skincurses-0.0.6.ebuild to use APIVERSION (vdr-skincurses-0.0.7.ebuild.diff,654 bytes, patch)
2006-09-19 15:19 UTC, Lucian Muresan
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Lucian Muresan 2006-09-19 15:17:37 UTC
Hi, I modified the vdr-skincurses ebuild to use the APIVERSION, hence the installed VDR version and not a hard-coded old onel hope this is useful.
Comment 1 Lucian Muresan 2006-09-19 15:19:49 UTC
Created attachment 97465 [details, diff]
adapts vdr-skincurses-0.0.6.ebuild to use APIVERSION

works for me, as vdr-skincurses-0.0.7 tested with vdr-1.4.1
Comment 2 Matthias Schwarzott gentoo-dev 2006-09-19 16:09:40 UTC
First: APIVERSION and VDRVERSION is not the same, thus vdr-${APIVERSION} works most of the time but not always.

And now the ko-criteria:
It is not allowed to modify ebuild metadata - SRC_URI, etc. dynamically

This metadata is cached and dynamic destroys the cache-consistence.
You can start reading about this here:
http://devmanual.gentoo.org/general-concepts/portage-cache/index.html

Thus closed as invalid.

It works as it is now. If a newer vdr-version also contains a newer skincurses-plugin we make a new ebuild-version for it.
Just leave us a note if this is the case and we don't know about it.
Comment 3 Matthias Schwarzott gentoo-dev 2006-09-21 06:40:33 UTC
Btw. I added vdr-skincurses-0.0.8 to portage (contained in vdr-1.4.2-3)