| Re: [proaudio] New RT kernel... how to update the ebuild? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] New RT kernel... how to update the ebuild?
- From: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Thu, 14 Apr 2011 19:48:46 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Thu, 14 Apr 2011 19:32:15 +0200,
Dominique Michel <dominique.michel@xxxxxxxxx> a écrit :
> Le Thu, 14 Apr 2011 18:37:44 +0200,
> Dominique Michel <dominique.michel@xxxxxxxxx> a écrit :
>
> > Le Thu, 14 Apr 2011 11:33:35 +0200,
> > Xavier Miller <xavier.miller@xxxxxxxxx> a écrit :
> >
> > > Hello,
> > >
> > > A new RT kernel is out : 2.6.33.9-rt31
> > >
> > > I tried to adapt an existing URL, but the problem is that the
> > > vanilla kernel is a "long term" version. If I set the "long term"
> > > flag in the ebuild, the RT patch has a wrong naming.
> > The kernel-2 eclass is in the eclass directory of portage. It is
> > quite complicated and don't have the time to look at it.
> >
> > An alternative way to get the right files would be to use:
> >
> > ##ATTENTION: hard-coded versions !
> > RT_PATCH="patch-2.6.33.9-rt31.bz2"
> > KERNEL_URI="http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6..33/linux-2.6.33.9.tar.bz2";
> >
> > into the ebuild.
> >
> > In general, any variable defined into an ebuild will take over the
> > same variable defined somewhere else (into the kernel-2 eclass in
> > this case)-
>
> Other things are going wrong. portage get the right files but it is
> considering the 2.6.33.9 kernel like a 2.6.33, and it want to patch it
> in order to get 2.6.33.9.
>
> Here is my solution, but I am sure that it must be another one and
> more elegant one:
>
> RT_PATCH="patch-2.6.33.9-rt31.bz2"
> KERNEL_URI="http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.33/linux-2.6.33.9.tar.bz2";
> OKV="2.6.33.9"
> UNIPATCH_LIST_DEFAULT=""
>
I get something better:
##ATTENTION: hard-coded version !
RT_PATCH="patch-2.6.33.9-rt31.bz2"
RESTRICT="mirror"
DESCRIPTION="Realtime Preemption patched low latency Linux kernel"
SRC_URI="${KERNEL_URI}
http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.33/patch-2.6.33.9..bz2
http://www.kernel.org/pub/linux/kernel/projects/rt/${RT_PATCH}
http://www.kernel.org/pub/linux/kernel/projects/rt/older/${RT_PATCH}";
>
> >
> > Ciao,
> > Dominique
> >
> > >
> > > Can someone help me to bump that version?
> > >
> > > Kind regards,
> > > Xavier Miller.
> > >
> > >
> > >
> >
> >
>
>
--
"We have the heroes we deserve."