mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist recommend linux version
Date: Thu, 8 Jan 2015 14:16:43 +0100	[thread overview]
Message-ID: <20150108131640.GA2046@omega> (raw)
In-Reply-To: <54AE807A.4020805@lespocky.de>

Hi,

On Thu, Jan 08, 2015 at 02:04:58PM +0100, Alexander Dahl wrote:
> Hei hei,
> 
> On 08.01.2015 12:57, Bilal TAŞ wrote:
> > Which Linux version is recommend ptxdist ? Debian or ubuntu or Centos ?
> 
> From my personal experience: it works with Debian and Ubuntu, I never
> tried anything else. But you can probably use any GNU/Linux distribution
> you prefer. ptxdist depends on very few host packages every modern
> GNU/Linux distribution should provide. There are even people using
> ptxdist on BSD based operating systems like Max OS X. Try what you like,
> if you experience any problems due to your chosen distro, report.
> 

I use Arch and can't recommend it, because I think I am the first guy
who detect issues with newer versions, like toolchain build with
make 4.0 and the changed sed version string.

These things are all well fixed now. For me, it's good to using
newer software, so ptxdist can prepare to the upcomming changes.

For Debian and Ubuntu, I would only use the stable branch of debian or
Ubuntu LTS [0] version. Then you have _maybe_ no issues if you using a older
ptxdist or toolchain version. But then it's the question if you really
want to use a older ptxdist or toolchain version.

- Alex

[0] https://wiki.ubuntu.com/LTS

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-01-08 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 11:57 Bilal TAŞ
2015-01-08 13:04 ` Alexander Dahl
2015-01-08 13:16   ` Alexander Aring [this message]
2015-01-08 13:27     ` Martin Hejnfelt

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=20150108131640.GA2046@omega \
    --to=alex.aring@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