pkgsrc-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: pkgsrc/shells/standalone-tcsh



Well, strongly recommend away, but pkgsrc was not designed for the people doing bulk builds, but rather for users. Nor should it ever be anything other than for those same users.

If pkgsrc becomes a place where only people with access to large company cloud deployments, or huge bulky machines, are happy, then I think we have a serious problem. Analogous to Linux being taken over by the corporate suits wanting to stress the number of lines of code they contribute. I really don't want to go there.

In much the same way that you seem to insist on PLISTs as being essential tools of pkgsrc itself, and I assert that they are large barriers to anyone anywhere packaging software, and on which we don't agree, I suspect that we'll have to differ until the cows come home.

Regards,
Alistair

On 11 September 2016 at 07:16, Jonathan Perkin <jperkin%joyent.com@localhost> wrote:
* On 2016-09-10 at 17:43 BST, Alistair Crooks wrote:

> This package does not violate anything, it redefines a pkgsrc variable.
>
> The package is not going away, so deal.
>
> Indeed, given the usefulness of this, I do wonder if we shouldn't be
> packaging more shells like this.

It kills bulk builds unless the user is very careful, and we already
have ugly hacks in standalone-tcsh to avoid this on certain platforms.
Therefore I would strongly recommend coming up with a robust mechanism
where this cannot happen before expanding it to more shells,
especially those which are more popular than tcsh, if we are to
persist with such packages.

--
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com




Home | Main Index | Thread Index | Old Index