public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] ARM64 and Debian LTS
Date: Thu, 19 Apr 2018 13:04:08 +0100	[thread overview]
Message-ID: <1524139448.2587.14.camel@codethink.co.uk> (raw)
In-Reply-To: <87efjcjudi.fsf@mid.deneb.enyo.de>

On Wed, 2018-04-18 at 19:29 +0200, Florian Weimer wrote:
> * Ben Hutchings:
> 
> > The list of architectures for jessie LTS is not decided and I haven't
> > seen any discussion of it yet.??The starting point for discussion would
> > be the list of architectures included in Debian 7 LTS, and that didn't
> > include arm64 because it wasn't in Debian 7 to start with.
> > 
> > I think that a proposal to include arm64 in Debian 8 LTS would probably
> > be accepted.??There should be no practical issues with maintaining the
> > infrastructure for it as arm64 hardware is only becoming more easily
> > available.
> 
> Does it???I don't think there is any commercially viable, server-class
> arm64 hardware you can buy today.??How can you promise long-term
> support for hardware that does not actually exist?

Debian prefers but doesn't absolutely require server type systems. 
None of the existing ARM (32-bit) or MIPS systems used as Debian
buildds or porterboxes appear to be designed as servers.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

      reply	other threads:[~2018-04-19 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 13:52 [cip-dev] ARM64 and Debian LTS Agustín Benito Bethencourt
2018-04-16 14:23 ` Jan Kiszka
2018-04-16 14:34   ` Wolfgang Mauerer
2018-04-17  6:43     ` Zoran S
2018-04-16 15:07   ` Agustín Benito Bethencourt
2018-04-18 14:47     ` Ben Hutchings
2018-04-18 17:29       ` Florian Weimer
2018-04-19 12:04         ` Ben Hutchings [this message]

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=1524139448.2587.14.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox