[mythtv-users] Gentoo 0.28 ebuild

[Hika van den Hoven]

Hoi Karl,

Tuesday, April 19, 2016, 10:32:57 PM, you wrote:

> On Tue, Apr 19, 2016 at 1:21 PM, Hika van den Hoven <hikavdh at gmail.com>wrote:

> Hoi Karl,
>  

>  Tuesday, April 19, 2016, 10:13:33 PM, you wrote:
>  
 >> On Tue, Apr 19, 2016 at 12:36 PM, Hika van den Hoven <hikavdh at gmail.com>wrote:
>  
 >> Hoi Rich,
 >>
>  
 >>  Tuesday, April 19, 2016, 8:23:52 PM, you wrote:
 >>
  >>> On Tue, Apr 19, 2016 at 1:59 PM, Bill Meek <keemllib at gmail.com> wrote:
  >>>> On 04/19/2016 11:28 AM, Rich Freeman wrote:
  >>>>>
  >>>>> On Tue, Apr 19, 2016 at 12:08 PM, Stuart Auchterlonie
  >>>>> <stuarta at squashedfrog.net> wrote:
  >>>>>>
  >>>>>>
  >>>>>> All the original logging methods still exist.
  >>>>>> ie. syslog, to file(s)
  >>>>>>
  >>>>>> The only real logging change is disabling the logserver
  >>>>>> by default.
  >>>>>>
  >>>>>> Personally i always use logging to files, because i'm running
  >>>>>> both 0.28 and master in parallel to aid development.
  >>>>>>
  >>>>>
  >>>>> Thanks - just to clarify.  Does logging to file work without logserver
  >>>>> enabled at build time?  If the backend itself and its children can log
  >>>>> directly to file/syslog that is fine by me, and seems similar to how
  >>>>> things used to work before the logserver came along.
  >>>>
  >>>>
  >>>> Yes. mythAnyprogram without mythlogserver running will log as directed
  >>>> by its --logpath or --syslog switches.
  >>>>
 >>
  >>> In that case, would a Gentoo OpenRC user mind doing a test for me?
  >>> Edit the mythtv-0.28.ebuild file and comment out or delete the
  >>> following line:
  >>>         use systemd || myconf="${myconf} $(use_enable mythlogserver)"
 >>
  >>> Then install mythtv and let me know if your logging is working exactly
  >>> as it did before.  It sounds like it should.  I'll update the ebuild
  >>> again after we get the results of testing in...
 >>
  >>> --
  >>> Rich
  >>> _______________________________________________
 >>
 >>  More then a year ago I fiddled with ebuilds.
 >>  - What again were the commands to create the manifest?
 >>  - Does the PORTDIR_OVERLAY variable still work the same (after the
 >>    changes to sync)?
 >>
>  
 >> 1. ebuild /usr/local/portage/media-tv/mythtv/mythtv-0.28.ebuild digest
>  
 >> 2. Not sure what you mean about "work the same". I haven't tested
 >> it lately but if you put an ebuild with the same name into the
 >> appropriate overlay directory, it will override the one in /usr/portage/
>  
>  
 >> Karl
>  
>  Last year there was that news message about sync because of the move
>  to git. In that message there were als references to overlays. But it
>  does seem to work the same with local overlays. I just wanted to be
>  sure without spending an hour or more searching through gentoo
>  documents. I have before found up-to-date documentation on these
>  changes to be scarce.


> Ah, okay. I remember reading about the switch to git, but I don't
> recall reading that it would affect overlays. Since epatch-user
> works quite well I haven't needed to create or tweak ebuilds for some time.


> Karl

This weekend I started a reinstall with a fresh stage3 for my laptop
and it suddenly had a package.use and a package.mask directory. I
didn't look deep, but I saw no reference. Anyhow they should
append '.d' to such a directory. There are a lot changes going on.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens