On 9/14/14, 11:40 AM, Julian Elischer wrote:
On 9/14/14, 2:32 AM, Craig Rodrigues wrote:
Technically, I agree with you that people should write portable shell
scripts,
and use #!/usr/bin/env bash rather than #!/bin/bash.
Pushing that behavior upstream is not always practical these days,
where
FreeBSD is in the minority, while Linux and MacOS X are in the vast
majority of where
people are doing development and learning how to write shell
scripts these
days.
I agree with Craig here.
we can keep our code "pure" but the standard shell these days for
everyone except us is /bin/bash.
There is nothing wrong with FreeSBD deciding that an industry
standard should be adopted..
While I don't like it when people code stuff at work in bash instead
of sh, I have to admit it has a lot of
advantages, and I can't really stop them.. It's getting more and
more common so to some extent we should
probably hide our pride a bit and look at bash (and maybe vim) and
giving them better standard support.
mailing the symlink is a really small thing.
err.. making
also I would like to RE-propose some suggestions that I've been making
now for nearly 15 years.
That we probably should have (at least) two classes of ports.
in the current system we have "base" and "ports"
I think we need more granularity than that.
at a minimum we should have Base, Base ports, and extended ports.
where "base ports" Must work, and a failure would be enough to hold up
a release.
"base" might contain extra hooks for "base ports" stuff.
Stuff in base-ports would include sendmail, bind, Xorg, maybe
appache, openldap, sasl,
possibly even the compilers.
Base ports get special priviledges, and responsibilities.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
