[mythtv-users] Re: [mythtv] Call for testers of release-0-18-fixes branch

[Karsten Jeppesen]

Jarod Wilson wrote:

>On Thursday 12 May 2005 15:59, Karsten Jeppesen wrote:
>  
>
>>Jarod Wilson wrote:
>>    
>>
>>>In an effort to get a 0.18.1 release out the door, we need more folks to
>>>test
>>>      
>>>
>>
>--target i686 and --target i386 build are negligible. When using --with 
>proc_opt, you might see a worthwhile improvement, but you obviously need to 
>build with that on your own system.
>  
>
That's why I asked. Thanks

>  
>
>>2) BuildRequires:  XFree86-devel (mythtv and mythplugins)
>>Hmm, I thought that was depreciated. Using xorg-x11-devel instead
>>    
>>
>
>Actually, xorg-x11-devel Provides: XFree86-devel, and setting the BuildReq to 
>XFree86-devel allows the same spec to be used on older distros with XF86.
>  
>
Duh -  I hadn't seen that.

>
>>4) Build requires libmyth stuff - is there a cross reference problem?
>>    
>>
>
>For the plugins or the main package itself?
>  
>
Both - but drop that since I was just looking high and low to why I 
couldn't compile. The moc stuff has nothing to do with the moc player. 
Most likely it was the missing .rpmmacros file.

>  
>
>>5) rm %{buildroot} depreciated
>>The correct way to do it is:
>>[ "%{buildroot}" != "/" ] && rm -rf %{buildroot}
>>    
>>
>
>I suppose that would be better, though I don't build as root anyhow.
>  
>
Has nothing to do with that. It safeguards that the goon (that would be 
me) who builds the rpms not by accident gets a space after the / in the 
buildroot path.
If that happens you could damage the file system. It is just a 
recommended check.

>  
>
>>6) environment variables
>>Which ones to set and what are the default values?
>>Like _varlibdir
>>    
>>
>
>Ah, yes, those require some macros. I posted the required ones to the -users 
>list a few weeks back, and they can be found in the atrpms-devel archives as 
>well. I'd just hit gossamer-threads and search for _varlibdir. Sorry 'bout 
>that, I only pushed the srpms up as an after-thought. :-)
>  
>
Got it. Why not put them in the spec file itself? I have never used the 
local macro file before so that is why I am asking.
I would define the dependent ones in the spec and then the 
environmentals in the .rpmmacros :

.rpmmacros:
%packager Scott White
%distribution Millnet RPMS
%vendor jtfltd.co.uk
%_signature gpg
%_gpg_name Scott White
%_topdir /home/sw25481/redhat
%_tmppath /var/tmp/rpm
%_rpmtopdir %{_topdir}/%{name}
%_builddir %{_tmppath}/BUILD
%_rpmdir %{_rpmtopdir}
%_sourcedir %{_rpmtopdir}
%_specdir %{_rpmtopdir}
%_srcrpmdir %{_rpmtopdir}


in the spec file
%define    _varlibdir        /var/lib
%define   _varcachedir   /var/cache
%define   _initdir            /etc/rc.d/init.d
%define   _sysconfigdir   /etc/sysconfig
%define   _logrotatedir    /etc/logrotate.d
%define   _logdir            /var/log
%define   _rundir            /var/run
%define   _subsysdir       /var/lock/subsys

That would allow you to compile whereever you want.


Just got mythtv compiled - pheww - now to the plugins...

Karsten