All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enrico <ebutera@users.sourceforge.net>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
	Sergey Lapin <slapin@ossfans.org>,
	Nicolas Aguirre <aguirre.nicolas@gmail.com>,
	OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: Re: meta-sunxi maintained?
Date: Tue, 28 May 2019 12:56:28 +0200	[thread overview]
Message-ID: <CA+2YH7vhko+jG6UTKHJrXGnv7AsCJP=GT4=trUUgkQ8cNQ5-0Q@mail.gmail.com> (raw)
In-Reply-To: <CAAfyv36hNk8CXYEfYASZJ-tOPEUwZ23i1zyDdLbVWk6r9ONkDA@mail.gmail.com>

On Tue, May 28, 2019 at 12:06 PM Dimitris Tassopoulos <dimtass@gmail.com> wrote:
>
> >
> > I was thinking about this also, too. The only reason is that in meta-sunxi they do a great job and they keep their layer clean, which is great I think. The other layers are just based on the armbian distro, which is a lot different, but for me it was much easier to integrate their patches, patching scripts and bootloader scripts to a Yocto layer. That way the only thing I do is that from time to time I just integrate their new patches and that's it. There's no development in the layer is just re-use of the armbian work and a wrapper around it. Therefore, it's hard, even no doable to put those different architectures together. But definitely that decision also bothered me a lot before I create the layer and I also don't like time to be spend on the same thing from different people. Nevertheless, from my point of view I couldn't find a way to put those things together. I've tried but I couldn't do it.
> >
> > Therefore, it was easier for me to do it the way I've done it. And after all, although it doesn't seem right, at the same time this is the beauty of the open source. I think the layers are just incompatible in the way that they are do things. Also it's not bad to have alternatives.
> >
> > Sunxi is a great community and I believe many of the armbian patches are coming from there. Others not. Of course, having them all together would be nice. But I don't think that it's possible because of the different approach.

It would be great to integrate all those different layers in
meta-sunxi,the main problem is that usually they come with their own
bootloader/kernel/etc.... so you have to *maintain* all these
different configurations.
Infact in the past i refused to do such things because i didn't have
the time to maintain all those different versions, it was just easier
to support what was already in mainline uboot/kernel.

But of course if someone wants to do it then it's welcome, the worst
thing that can happen is that once an arch gets unmaintained it will
be removed.

One thing that can be done anyway is to have those external layers
linked in the readme, so at least people will know they exist.

Enrico


  reply	other threads:[~2019-05-28 10:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 14:49 meta-sunxi maintained? Belisko Marek
2019-05-27 15:44 ` Enrico
2019-05-27 17:32   ` Belisko Marek
2019-05-28  8:31     ` Maciej Pijanowski
2019-05-28  9:53       ` Belisko Marek
2019-05-28  9:01     ` Dimitris Tassopoulos
2019-05-28  9:49       ` Belisko Marek
2019-05-28  9:49         ` [yocto] " Belisko Marek
2019-05-28 10:05         ` Dimitris Tassopoulos
2019-05-28 10:11           ` Belisko Marek
2019-05-28 10:11             ` [yocto] " Belisko Marek
2019-05-28 10:56             ` Enrico [this message]
2019-05-28 11:06               ` Dimitris Tassopoulos
2019-05-29  6:36                 ` Belisko Marek
2019-05-29  6:36                   ` [yocto] " Belisko Marek
2019-05-29  7:03                   ` Dimitris Tassopoulos
2019-05-29  7:39                     ` Belisko Marek
2019-05-29  7:39                       ` [yocto] " Belisko Marek
2019-05-29  8:03                       ` Dimitris Tassopoulos
2019-05-29  8:17                         ` Belisko Marek
2019-05-29  8:17                           ` [yocto] " Belisko Marek
2019-05-29  8:38                       ` Maciej Pijanowski
2019-05-29 11:23                         ` Belisko Marek
2019-05-31  6:47                         ` Belisko Marek
2019-05-31  6:49                           ` Maciej Pijanowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+2YH7vhko+jG6UTKHJrXGnv7AsCJP=GT4=trUUgkQ8cNQ5-0Q@mail.gmail.com' \
    --to=ebutera@users.sourceforge.net \
    --cc=aguirre.nicolas@gmail.com \
    --cc=marek.belisko@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=slapin@ossfans.org \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.