On 27.04.14 17:23, Matwey V. Kornilov wrote:
>
>
> I don't know. If it is the best solution, then we can. Basically, what
> I need is to fetch the 11 patches from Kernel:openSUSE-13.1
> However, I am not aware of how does kernel updates usually get into
> Ports tree.
>
Please don't top post :).
I don't think we have a really good solution for this. The "usual" way
we envisioned things to work is that openSUSE:<release> just contains
everything necessary for the release.
Any board we have to enable after that process should just get a Contrib
subproject where we can add newer versions of kernels etc specific to
that board. In parallel all the changes go into Factory where we can
then enable that board for the next <release> version of openSUSE.
However, getting hardware support working for a release is so incredibly
hard that I'm fairly sure we'd end up with an empty set of hardware
platforms if we really went with that plan. So we started loosing up the
requirements. I'm not sure up to which point it does make sense to
loosen them though.
Would it help you if we create a Contrib for the BeagleBone and add you
as admin for that? There you could linkpac the JeOS package inside and
copypac the latest kernel and then have your own playing ground for that
particular platform without necessarily relying on us.
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org