Hallo,
nachdem das XBMC-Addon-xvdr XBMC direkt und zuverlässig zum Absturz bringt, dachte ich mir, könnte ich ja mal die Fallbackvariante VNSI-Server testen. Das Plugin auf XBMC-Seite ist ja bereits in XBMC integriert. Beim VDR sieht das leider anders aus.
vdr-vnsiserver-9999-r1.ebuild:
pkg_setup() {
eerror "vdr-vnsiserver is dead on upstream"
eerror "project has changed to:"
eerror "https://github.com/pipelka/vdr-plugin-xvdr"
eerror "See detailed info for this"
eerror "https://github.com/pipelka/vdr-plugin-vnsiserver/blob/master/README"
eerror "Please use media-plugins/vdr-xvdr from portage"
die || "dead on upstream, use media-plugins/vdr-xvdr"
}
Alles anzeigen
Und vdr-vnsiserver-9999.ebuild findet die Git-Repo nicht mehr:
Den Fork findet man unter: https://github.com/FernetMenta/xbmc/tree/vnsi
Nur leider hab ich's nicht hinbekommen, das Ebuild so zu ändern, dass ich das Plugin trotzdem irgendwie compiliert bekomm.
/etc/portage/env/media-plugins/vdr-vnsiserver
EGIT_REPO_URI="git://github.com/FernetMenta/xbmc.git"
EGIT_BRANCH="vnsi"
EGIT_PROJECT="vdr-vnsi"
macht bei mir dann folgendes:
emerge -1 =vdr-vnsiserver-9999
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) media-plugins/vdr-vnsiserver-9999 from vdr-devel
* please use append-cppflags for preprocessor flags
* Compiling against
* vdr-1.7.27 [API version 1.7.27]
>>> Unpacking source...
Cloning into bare repository '/var/portage/distfiles/egit-src/vdr-vnsi'...
remote: Counting objects: 186414, done.
remote: Compressing objects: 100% (58555/58555), done.
remote: Total 186414 (delta 134887), reused 171016 (delta 124081)
Receiving objects: 100% (186414/186414), 322.50 MiB | 701 KiB/s, done.
Resolving deltas: 100% (134887/134887), done.
GIT NEW clone -->
repository: git://github.com/FernetMenta/xbmc.git
at the commit: a4920178afeb919e8bc070731f9030892e76594a
branch: vnsi
storage directory: "/var/portage/distfiles/egit-src/vdr-vnsi"
checkout type: bare repository
Cloning into '/var/tmp/portage/media-plugins/vdr-vnsiserver-9999/work/vnsiserver-9999'...
done.
Checking out files: 100% (14014/14014), done.
Branch branch-vnsi set up to track remote branch vnsi from origin.
Switched to a new branch 'branch-vnsi'
>>> Unpacked to /var/tmp/portage/media-plugins/vdr-vnsiserver-9999/work/vnsiserver-9999
>>> Source unpacked in /var/tmp/portage/media-plugins/vdr-vnsiserver-9999/work
>>> Preparing source in /var/tmp/portage/media-plugins/vdr-vnsiserver-9999/work/vnsiserver-9999 ...
* Patching Makefile
* ERROR: media-plugins/vdr-vnsiserver-9999 failed (prepare phase):
* Makefile of plugin can not be found!
*
* Call stack:
* ebuild.sh, line 85: Called src_prepare
* environment, line 2858: Called vdr-plugin_src_prepare
* environment, line 3607: Called vdr-plugin_src_util 'prepare'
* environment, line 3639: Called vdr-plugin_src_util 'add_local_patch' 'patchmakefile' 'i18n'
* environment, line 3650: Called vdr_patchmakefile
* environment, line 3721: Called die
* The specific snippet of code:
* [[ -e Makefile ]] || die "Makefile of plugin can not be found!";
*
* If you need support, post the output of `emerge --info '=media-plugins/vdr-vnsiserver-9999'`,
* the complete build log and the output of `emerge -pqv '=media-plugins/vdr-vnsiserver-9999'`.
* This ebuild is from a repository named 'vdr-devel'
* The complete build log is located at '/var/tmp/portage/media-plugins/vdr-vnsiserver-9999/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/media-plugins/vdr-vnsiserver-9999/temp/environment'.
* Working directory: '/var/tmp/portage/media-plugins/vdr-vnsiserver-9999/work/vnsiserver-9999'
* S: '/var/tmp/portage/media-plugins/vdr-vnsiserver-9999/work/vnsiserver-9999'
>>> Failed to emerge media-plugins/vdr-vnsiserver-9999, Log file:
>>> '/var/tmp/portage/media-plugins/vdr-vnsiserver-9999/temp/build.log'
Alles anzeigen
Scheint so, als ob sich auch irgendwie die Verzeichnisstruktur im Plugin geändert hat. Sehr unschön das Ganze. Wie kriegt man das vnsiserver-Plugin zum Laufen?