mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Yocto
Date: Mon, 11 Sep 2017 11:25:53 +0200	[thread overview]
Message-ID: <CABDcavZ-0Q7d=jGp3A1-7yj5QqcD1L6pKA3Zvp7gO9FwJy-qDg@mail.gmail.com> (raw)
In-Reply-To: <1504962219.21495.392.camel@erwinrol.com>


[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]

Hello,

My team is using ptxdist for several projects on several different boards
and while
there are of course things that can be improved, we are very happy with it.

I have not used Yocto but have looked into it from time to time; my feeling
is that
it raises the level of abstraction too much ("too much" for my personal
preferences,
that is), thus making it difficult to see what is happening under the hood.
I share
your feeling that Yocto is becoming "the Ubuntu of the embedded world".

The main good thing about Yocto is that it is becoming hugely popular and
has a
very strong and active community. It would be great if the same would
happen with
ptxdist :-)

Guillermo

2017-09-09 15:03 GMT+02:00 Erwin Rol <mailinglists@erwinrol.com>:

> Hey all,
>
> yes I know the topic is blasphemy ;-)  but I was wondering if there are
> ppl that made usecase comparisons between ptxdist and Yocto? My personal
> experience with small systems (no GUI/X/wayland) is that ptxdist is
> really easy to get going. With large systems that need QT 5.9,
> webkitgtk/chromium, different OpenGL versions etc. is that ptxdist is
> not always that easy. But I am not experienced enough with Yocto to say
> if that will be easier/better.
>
> So hence the question, anybody out there that tried both and picked
> ptxdist (or yocto) for a reason ?
>
> - Erwin
>
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de




-- 
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 2273 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2017-09-11  9:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-09 13:03 Erwin Rol
2017-09-09 15:54 ` Enrico Weigelt, metux IT consult
2017-09-09 16:33   ` Erwin Rol
2017-09-10 19:24     ` Enrico Weigelt, metux IT consult
2017-09-10 20:09       ` Erwin Rol
2017-09-09 18:36 ` Tim Sander
2017-09-10 19:16   ` Robert Schwebel
2017-09-12 18:42     ` Tim Sander
2017-09-12 20:12       ` Robert Schwebel
2017-09-12 21:33         ` Tim Sander
2017-09-13  5:42           ` Robert Schwebel
2017-09-13 15:38       ` Michael Olbrich
2017-09-14 22:44         ` Tim Sander
2017-09-15  6:47           ` Michael Olbrich
2017-09-15 11:02             ` Alm, Michael
2017-09-16  9:25               ` Michael Olbrich
2017-09-10 19:13 ` Robert Schwebel
2017-09-11  9:25 ` Guillermo Rodriguez Garcia [this message]
2017-09-12 10:49   ` Alexander Dahl
     [not found] <20170911063001.A6FE73EC2A2E_9B62D69B@mail.eckelmann.de>
2017-09-11  7:14 ` Schenk, Gavin
2017-09-12 10:44   ` Alexander Dahl
2017-09-12 13:29     ` Schenk, Gavin

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='CABDcavZ-0Q7d=jGp3A1-7yj5QqcD1L6pKA3Zvp7gO9FwJy-qDg@mail.gmail.com' \
    --to=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox