From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] Define minimal supported kernel and (g)libc version
Date: Tue, 17 Mar 2020 10:04:12 +0100 [thread overview]
Message-ID: <20200317090412.GA31467@dell5510> (raw)
In-Reply-To: <CAEemH2dCckuUw=x-yKpBe4FpjTdovytSqpOoRSTFiR96_ECeDA@mail.gmail.com>
Hi Li,
> > The oldest system in travis we have CentOS 6: kernel-2.6.32 / glibc-2.12 /
> > gcc-4.4.7 (clang-3.4.2, but we don't test it with clang). I'm ok to have
> > this
> > older dependency, just to make sure it builds. But code would be cleaner
> > for
> > sure if we drop it.
> +1
> Sounds good to me.
I'm sorry, are you for removing CentOS 6 from Travis or not?
> > BTW I also occasionally test build on SLES 11-SP3 (kernel 3.0 /
> > glibc-2.11.3 /
> > gcc-4.3.4 - older glibc and gcc), but this is not even in travis.
> > But for testing these distros we use older releases (the same mentioned
> > Jan [1]).
> Agreed, we can explicitly declare that(in some place of Doc) from a
> specific LTP(e.g ltp-full-20200120) version, we don't provide code
> supporting for the older kernel/glibc/gcc package anymore. If people who
> are going to test old distros, they can just pick up an old released LTP
> version and hack it by themself. The latest branch of LTP doesn't accept
> that patch for old things.
+1
Kind regards,
Petr
next prev parent reply other threads:[~2020-03-17 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 14:14 [LTP] [RFC] Define minimal supported kernel and (g)libc version Petr Vorel
2020-03-14 8:01 ` Li Wang
2020-03-17 8:15 ` Petr Vorel
2020-03-17 8:53 ` Li Wang
2020-03-17 9:04 ` Petr Vorel [this message]
2020-03-17 9:27 ` Li Wang
2020-03-19 12:48 ` Jan Stancek
2020-03-21 6:46 ` Petr Vorel
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=20200317090412.GA31467@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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.