Date: Tue, 18 Oct 2022 15:07:25 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: FreeBSD User <freebsd@walstatt-de.de> Cc: src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: Re: git: 497cdf9673ec - main - sh: read more profile files. Message-ID: <8635blz3ea.fsf@ltc.des.no> In-Reply-To: <20221009091405.171bde4f@thor.intern.walstatt.dynvpn.de> (FreeBSD User's message of "Sun, 9 Oct 2022 09:13:38 %2B0200") References: <202210012131.291LVIY8044703@gitrepo.freebsd.org> <20221009091405.171bde4f@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD User <freebsd@walstatt-de.de> writes:
> According to this commit, I took the liberty opening a PR (id=3D266913) b=
ecause some ports, like
> lang/gawk and x11-toolkits/vte3, install their SH and CSH set of shell co=
nfiguration files into
> ${LOCALBASE}/etc/profile.d/, i.e. vte.{sh|csh}.=20
> The proposed/commited /etc/profile includes also *.csh files, which trigg=
ers some disturbing
> error messages during a full login (i.e. su - ) and the list of those mes=
sages increase with
> the number of unfitting shell configuration files.
> I do not have a general solution, maybe someone more enlighted can take a=
look at this.
I've been racking my brain over this because I can't think of another
solution than to either explicitly skip *.csh, or only read *.sh. The
Linux distros I was able to check easily (RHEL, Debian, Ubuntu, Alpine)
do the latter, so I suppose we should too.
DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8635blz3ea.fsf>