Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On 02/17/2012 02:12 PM, Neil Bothwick wrote: > On Fri, 17 Feb 2012 12:59:32 +0200, Alan McKinnon wrote: > > The MythTV overlay is not serviced by layman. Instead, it includes > a script called from /etc/portage/postsync.d/ to update itself > after every emerge --sync. > > Basically, there are two types of portage tree, ones you manage > yourself and one that are managed remotely and synced to your > system. The latter includes the main portage tree, all layman > overlays and the MythTV one. Only fiddle with the former. Much clearer now, thanks to you and Alan. I'll try to do it the proper way. raf
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On Fri, 17 Feb 2012 12:59:32 +0200, Alan McKinnon wrote: > ebuilds do not update themselves, something else does. > > All an overlay is, is an alternate bunch of ebuilds laid out in the > same format as the portage tree. Layman is nothing more than a nice > bunch of scripts that automate the install, update and resync aspect of > using them. The process you just described makes no sense to me at all > unless it is some customization you did yourself. The MythTV overlay is not serviced by layman. Instead, it includes a script called from /etc/portage/postsync.d/ to update itself after every emerge --sync. > But step back and look at this logically. You have a copy of a file > that gets updated from a repo somewhere. But you are also fiddling > around with the same file and expecting it to all magically just work > without collisions despite having two agents fooling around with it. > > Does that strike you as a good idea? Now that you understand how it works, I hope you can see that your comments still make absolute sense. Basically, there are two types of portage tree, ones you manage yourself and one that are managed remotely and synced to your system. The latter includes the main portage tree, all layman overlays and the MythTV one. Only fiddle with the former. -- Neil Bothwick If you think talk is cheap, try hiring a lawyer. signature.asc Description: PGP signature
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On Fri, 17 Feb 2012 11:39:24 +0100 Raffaele BELARDI wrote: > On 02/17/2012 11:18 AM, Alan McKinnon wrote: > > On Fri, 17 Feb 2012 09:01:36 +0100 > > Raffaele BELARDI wrote: > >> The change was done in the mythtv overlay > >> (/usr/local/mythtv_portage/), would that be overwritten by a > >> resync? I understood that overlay gets updated only when there is > >> a mythtv update upstream. > > > > It will be overwritten with every layman update/resync > > > > layman will notice that you have a file that is different from the > > repo and will revert it, and you cannot stop this happening. It > > does not depend on whether the remote file has changed, it only > > depends on you locally having a file that is different to the repo. > > > > Seriously, the gentoo docs are full or warning to not do what you > > did. Use the local overlay, it was designed for exactly this > > purpose. > > I'm probably oversimplifying because I don't know much about overlays. > > I'm not using layman at all but I am using a local overlay for mythtv. > From what I understand the 'overlayed' mythtv ebuild is responsible > for the overlay update though a script installed > in /etc/portage/postsync.d/ which basically performs a 'git pull'. So > unless there is a new git snapshot upstream the modified ebuild will > not get overwritten, correct? I have no idea what you are talking about actually. ebuilds do not update themselves, something else does. All an overlay is, is an alternate bunch of ebuilds laid out in the same format as the portage tree. Layman is nothing more than a nice bunch of scripts that automate the install, update and resync aspect of using them. The process you just described makes no sense to me at all unless it is some customization you did yourself. But step back and look at this logically. You have a copy of a file that gets updated from a repo somewhere. But you are also fiddling around with the same file and expecting it to all magically just work without collisions despite having two agents fooling around with it. Does that strike you as a good idea? The sane way to do this is to leave the remote repo alone and let it do it's thing when and how it wants to using layman. You will then always have an ebuild synced to upstream. Copy the ebuild you feel you need to modify to PORTDIR_OVERLAY and make your changes there. Portage will use your customized ebuild in preference to the one from the overlay (due to priority rules) so all is good. When the ebuild in the git repo is updated, the version number will be bumped and portage will then use that one in preference to your local copy (due to version number being higher). If that ebuild doesn't quite work for you yet, copy it to PORTDIR_OVERLAY and make your custom changes there. keep doing this, rinse and repeat, until the upstream repo gets their act together. -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On 02/17/2012 11:18 AM, Alan McKinnon wrote: > On Fri, 17 Feb 2012 09:01:36 +0100 > Raffaele BELARDI wrote: >> The change was done in the mythtv overlay >> (/usr/local/mythtv_portage/), would that be overwritten by a resync? >> I understood that overlay gets updated only when there is a mythtv >> update upstream. > > It will be overwritten with every layman update/resync > > layman will notice that you have a file that is different from the repo > and will revert it, and you cannot stop this happening. It does not > depend on whether the remote file has changed, it only depends on you > locally having a file that is different to the repo. > > Seriously, the gentoo docs are full or warning to not do what you did. > Use the local overlay, it was designed for exactly this purpose. I'm probably oversimplifying because I don't know much about overlays. I'm not using layman at all but I am using a local overlay for mythtv. >From what I understand the 'overlayed' mythtv ebuild is responsible for the overlay update though a script installed in /etc/portage/postsync.d/ which basically performs a 'git pull'. So unless there is a new git snapshot upstream the modified ebuild will not get overwritten, correct? raf
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On Fri, 17 Feb 2012 09:01:36 +0100 Raffaele BELARDI wrote: > On 02/17/2012 08:48 AM, Alan McKinnon wrote: > > On Fri, 17 Feb 2012 08:19:33 +0100 > > Your changes will be overwritten and reverted next time you resync > > the portage tree and every time thereafter. > > > > Editing the ebuild is not the simplest route, it is a vastly more > > complex route. Instead, put the ebuild in the local overlay where > > portage knows not to touch it. A local overlay does not require > > layman. > > The change was done in the mythtv overlay > (/usr/local/mythtv_portage/), would that be overwritten by a resync? > I understood that overlay gets updated only when there is a mythtv > update upstream. It will be overwritten with every layman update/resync layman will notice that you have a file that is different from the repo and will revert it, and you cannot stop this happening. It does not depend on whether the remote file has changed, it only depends on you locally having a file that is different to the repo. Seriously, the gentoo docs are full or warning to not do what you did. Use the local overlay, it was designed for exactly this purpose. -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On 02/17/2012 08:48 AM, Alan McKinnon wrote: > On Fri, 17 Feb 2012 08:19:33 +0100 > Your changes will be overwritten and reverted next time you resync the > portage tree and every time thereafter. > > Editing the ebuild is not the simplest route, it is a vastly more > complex route. Instead, put the ebuild in the local overlay where > portage knows not to touch it. A local overlay does not require layman. The change was done in the mythtv overlay (/usr/local/mythtv_portage/), would that be overwritten by a resync? I understood that overlay gets updated only when there is a mythtv update upstream. raf
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On Fri, 17 Feb 2012 08:19:33 +0100 Raffaele BELARDI wrote: > On 02/16/2012 09:16 AM, Hinnerk van Bruinehsen wrote: > > On 16.02.2012 08:58, Raffaele BELARDI wrote: > >> I suppose that my only options for rebuilding mythtv are to wait > >> for upstream to update the ebuild or to update it myself. How > >> difficult would the latter be? > > > > If the package just moved from media-tv to virtual it's easy: > > > > You should make a private overlay and copy the ebuild with the > > dependency there: > > I went for a simpler route to just edit the ebuild and rebuild the > manifest. > > raf Your changes will be overwritten and reverted next time you resync the portage tree and every time thereafter. Editing the ebuild is not the simplest route, it is a vastly more complex route. Instead, put the ebuild in the local overlay where portage knows not to touch it. A local overlay does not require layman. -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On 02/16/2012 09:16 AM, Hinnerk van Bruinehsen wrote: > On 16.02.2012 08:58, Raffaele BELARDI wrote: >> I suppose that my only options for rebuilding mythtv are to wait >> for upstream to update the ebuild or to update it myself. How >> difficult would the latter be? > > If the package just moved from media-tv to virtual it's easy: > > You should make a private overlay and copy the ebuild with the > dependency there: I went for a simpler route to just edit the ebuild and rebuild the manifest. raf
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On Thu, 16 Feb 2012 09:16:42 +0100, Hinnerk van Bruinehsen wrote: > Some explanations: I would recommend creating an own overlay so you > don't get problems on sync. If multiple packages are concerned you'll > have to repeat the procedure (except the overlay creation) for each of > them. > If the package was'nt moved, but really changed, it may not be enough > to get everything working... Adding it to package.provided also works, although I went the overlay route as I only had to do that once to fix several boxes. -- Neil Bothwick Master of all I survey (at the moment, empty pizza boxes) signature.asc Description: PGP signature
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
On 02/16/2012 09:16 AM, Hinnerk van Bruinehsen wrote: > On 16.02.2012 08:58, Raffaele BELARDI wrote: >> I suppose that my only options for rebuilding mythtv are to wait >> for upstream to update the ebuild or to update it myself. How >> difficult would the latter be? > > If the package just moved from media-tv to virtual it's easy: > > You should make a private overlay and copy the ebuild with the > dependency there: > > mkdir /var/lib/layman/myoverlay/ mkdir > /var/lib/layman/myoverlay/profile echo "myoverlay" > > /var/lib/layman/myoverlay/profile/repo_name # Overlay is ready # > add /var/lib/layman/myoverlay/ to /var/lib/layman/make.conf (using > you favorite editor. If you make it the last entry it'll override > other overlays. Thanks, looks easy but I need to look into layman and overlays, I've never approached that before. In the meantime I found that another option is to auto-generate ebuilds from the mythtv overlay: http://www.mythtv.org/pipermail/mythtv-users/2011-February/309883.html raf
Re: [gentoo-user] linuxtv-dvb-headers gone virtual blocks mythtv overlay
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.02.2012 08:58, Raffaele BELARDI wrote: > After yesterday's sync I found mythtv's overlay not able to build > anymore due to missing dependency: media-tv/linuxtv-dvb-headers is > no longer present in the tree. A quick search shows that it has now > become virtual/linuxtv-dvb-headers [1]. > > I suppose that my only options for rebuilding mythtv are to wait > for upstream to update the ebuild or to update it myself. How > difficult would the latter be? > > raf > > [1] https://bugs.gentoo.org/show_bug.cgi?id=403929 If the package just moved from media-tv to virtual it's easy: You should make a private overlay and copy the ebuild with the dependency there: mkdir /var/lib/layman/myoverlay/ mkdir /var/lib/layman/myoverlay/profile echo "myoverlay" > /var/lib/layman/myoverlay/profile/repo_name # Overlay is ready # add /var/lib/layman/myoverlay/ to /var/lib/layman/make.conf (using you favorite editor. If you make it the last entry it'll override other overlays. mkdir /var/lib/layman/myoverlay/ #e.g. media-video for package-category cp -r / /var/lib/layman/myoverlay/ # e.g. cp -r /var/lib/layman/mythtv/media-video/mythtv /var/lib/layman/myoverlay/media-video Afterwards edit the ebuild with your favourite editor an replace the media-tv/linuxtv-dvb-headers with virtual/linuxtv-dvb-headers Then do (inside the directory of the package inside you own overlay): ebuild manifest then emerge and you're ready. You could send your modified ebuild to the mythtv-overlay maintainer/owner. Some explanations: I would recommend creating an own overlay so you don't get problems on sync. If multiple packages are concerned you'll have to repeat the procedure (except the overlay creation) for each of them. If the package was'nt moved, but really changed, it may not be enough to get everything working... Hope that helps! Kind regards, Hinnerk -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPPLtqAAoJEJwwOFaNFkYcSxMIAIB+pxzrSVubsdZ9teXH8BZ6 hzLYGAWxtDmvBTPMkb58xdjTkR33t1prQ+fnDbFHZ2BuGKCZfKnTknfhAxEoFA7n HQ/gR8Ad633P/A6wIsy3yWWEVac6GxzUfATVq1GPEJVlVbSItUASEEeq8wRgplWq A7jIDiveIhkQuGkSsZ0NuC0+V+YEeulWWNQLz/zZsfAqX9YyidALZYQLWE2n6GhM XJZiyF+QnOfPzwSyobdjwQD7W1QpmTshH1mvEF6QeA+HSk9a7HD5ElJVx+AKoFYs p3TE56IHgwuyQioApCl7YBQxFixYxrdo0EIbg00JOpU2vohv3G7/E5HHMimp7Ns= =1cAv -END PGP SIGNATURE-
