There is an onus on you to use the appropriate mailing list. Bug-bash isn't
for make-ing your case, bug-bash is for the bugs.
Dave Finlay
On Dec 6, 2016 15:44, "Robert Durkacz" wrote:
On 6 December 2016 at 00:19, Greg Wooledge wrote:
> what
On 6 December 2016 at 00:19, Greg Wooledge wrote:
> what evidence?
> [for shell scripting builds]
>
I suppose the evidence that you want is in the very same wikipedia article
about make, where it says precisely that shell scripts were used before
make came along.
On Mon, Dec 05, 2016 at 11:37:11PM +1100, Robert Durkacz wrote:
> I am asking about shell scripting
> of software builds, something that is perfectly possible to do and once
> must have been the common way.
Based on what evidence? Show me a shell script created to build a
software project
You have gone to some trouble with your answer Eduardo, and thanks for that
but really you are arguing against a proposition that I have not put and I
do not want other readers to be mislead. I am asking about shell scripting
of software builds, something that is perfectly possible to do and once
On Sat, Dec 3, 2016 at 11:07 AM, Eduardo Bustamante
wrote:
> "build market"? What are you talking about? make was created with the
> sole purpose of build automation. The shell was created to provide a
> "human interface" to computer operators. These are very specific and
>
"build market"? What are you talking about? make was created with the
sole purpose of build automation. The shell was created to provide a
"human interface" to computer operators. These are very specific and
different purposes. Are you going to start asking next to re-implement
vi inside bash? to
On Fri, Dec 02, 2016 Greg Wooledge wrote:
"For starters, make is *older* than bash, by over a decade.
"https://en.wikipedia.org/wiki/Make_%28software%29 says that make
originated at Bell Labs in April 1976.
"https://en.wikipedia.org/wiki/Bash_%28Unix_shell%29 says that the first
"beta version of
Robert-
I wanted to craft a witty retort with a veneer of encouragement that might
push your towards trying your proposed endeavor. I could not bring myself
to do it after realizing that you are quite serious. I understand your
motivations. Build systems are often complicated, opaque pieces of
On Fri, Dec 02, 2016 at 10:53:30PM +1100, Robert Durkacz wrote:
> really I am asking why should not program builds have been scripted with
> bash all along
For starters, make is *older* than bash, by over a decade.
https://en.wikipedia.org/wiki/Make_%28software%29 says that make
originated at
On 29/11/16 Charles Daffern replied to my question about bash and make as
if I was proposing that bash might beneficially reimplement make, but
really I am asking why should not program builds have been scripted with
bash all along and make never invented. So if Charles or someone else could
point
I agree that is the first step to take, but I am supposing that, since
build systems are a big business, some extensions to bash would be worth
doing to take on that market. E.g. I think we would need a concept of lists
of files so as to skip executing a command if all files in the list are
older
On 29/11/16 05:41, Robert Durkacz wrote:
> make has survived all this time but it is not very well accepted today
> with a lot of competing build systems trying to do better. bash is
> very secure and moreover the Bourne shell was there first. make is
> falling out of favour as far as I can see
make has survived all this time but it is not very well accepted today with
a lot of competing build systems trying to do better. bash is very secure
and moreover the Bourne shell was there first. make is falling out of
favour as far as I can see even though it has had a very good run:
Kernighan
On Sun, Nov 27, 2016 at 7:25 PM, Robert Durkacz
wrote:
> Has thought been given, over the years, to extending bash to do
> what make does, in the obvious way that I am about to describe?
>
> It would be a matter of having chosen build commands do nothing if their
>
Why should bash do what make already does?
15 matches
Mail list logo