From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/1] Remove old build scripts
Date: Tue, 24 Apr 2018 13:05:56 +0200 [thread overview]
Message-ID: <20180424110556.GB32248@rei> (raw)
In-Reply-To: <20180424101429.26799-1-pvorel@suse.cz>
Hi!
> These scripts are from CVS era, expect git://ltp.git.sourceforge.net.
> Although they have support for git and testing our make build system
> it's important, we use travis and anything important should be moved
> there.
I do agree here, let's apply this, unless anybody objects, next week.
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> BTW: my wish is to move from custom make build system to automake based.
> Why: 'make install' for Open POSIX testsuite is broken (some files are missing)
> and due being moved-in as sort of sub-project it's not easy to fix it.
> And we use autoconf anyway.
I do not like automake that much. To be honest I think that the whole
autotools suite is years behind the rest of the world, hence I would
consider moving to it to be a step back.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-04-24 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 10:14 [LTP] [RFC PATCH 1/1] Remove old build scripts Petr Vorel
2018-04-24 11:05 ` Cyril Hrubis [this message]
2018-04-27 9:03 ` 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=20180424110556.GB32248@rei \
--to=chrubis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox