<div dir="ltr"><p>Over the past year I've been working with both external major build
RPM systems to build RPMS for the projects I've been working on. <br></p><p>If posts appears incomplete, it was probably edited by the upstream admin.</p>
<p>Previously, I've had some (naive) idea's of bridging the two repo's to some extent. <br>
However, that idea was soley mine and did not receive support from where
it needed to be. I also recently had ambitions to move off of el6
completely and jump on the bandwagon to see if it was a smooth ride.
That was also overly idealistic and naive of me to think.</p>
<p>Given this. <br>
I now no longer ride this fence and try to please both parties. I now will focus on<br>
ATrpms compatible packages only. <br></p><p>If posts appears incomplete, it was probably edited by the upstream admin.</p>
<p>What does this mean technically?</p>
<p>It means I will not be using any Source RPMS they have been built at RPMfusion.<br>
I will still build missing packages that are not in ATrpms from EPEL or upstream.</p>
<p>It means the ffmpeg and other similar "moving target" packages that
Axel and the international community chooses will be matched to all
projects ELmythOS project uses.</p>
<p>It means RedHat EL6 based systems will still be supported to run
additional Qt 4.7/4.8 along side the builtin qt-4.6.2 in el6 proper.</p>
<p>It means I don't have to "reshape a wheel" too often and the result could be a more robust system.</p>
<p>If your more conservative than the most and prefer to use older
versions for stability over NEW functionality, look no further. Use el6
and mythtv-0.25.x.</p>
<p>If you want to play in the devel sandbox with the latest toys and
look really cool doing so, you should be on the latest releases of
everything. <br>
Regarding that, el7 is where the NEW fuctionality will be so if you want to play in the mythtv, qt sandbox, use el7 and repos. <br></p><p>If posts appears incomplete, it was probably edited by the upstream admin.</p>
<p>***Everyone understands devs want everyone to use their latest work, that they can be proud of. <br>
So I do not attempt to insult their innovation, but instead will offer alternatives<br>
of their older work, that I deem still relevently funtional. </p>
<p>I make my own decisions based on my experiences:<br>
as an End User,<br>
then as a Computer Technician,<br>
then as a former Technical Support worker,<br>
then as Linux Systems Admin<br>
and now as an aspiring Systems Builder, packager and developer.</p>
<p>If posts appears incomplete, it was probably edited by the upstream admin.</p><p>Note:<br>
I do not call myself an Engineer because I'm finishing my education
still and it would an insult to repected Engineers to do so. I've
learned everything I know with GED as my current HIGHEST EDUCATION. <br>
If I ever call myself an Engineer , you can bet your $T#$ I will back it
up with a Eng.Degree in Mathematics. For now I'm just a passionate
volunteer Gnobody systems builder with many opinions and high
expectations.</p>
<p>I know enough about C/C++ Software development right to be objective,
as my skills improve I will make patches as needed from upstream. This
should help the project stay updated with security updates.</p>
<p>I'm not running a popularity contest. Plenty do that already and miss the details I'm passionate about.</p><p>If posts appears incomplete, it was probably edited by the upstream admin.<br></p></div>