On വെള്ളി 09 ഡിസംബര്‍ 2016 09:47 വൈകു, John-David Dalton wrote:
>> So in debian we patch grunt to use globally installed modules and tasks.
> I'm OK with creating more hoops to jump through in this case. I think
> the approach you've outlined is a bit wonky. There are ways to bundle
> deps without flattening versions. You could package grunt, gulp, and
> whatever else in ways that avoid the need for versionless dependents, by
> way of self contained packages.

That means we have to maintain multiple copies of the same library and
that increases our effort to maintain it. If we want to fix a bug in a
library, we will have to update all the packages bundling that library.
We have been doing it this way for all the languages, even though nodejs
developers feel they are special.

When we update a dependency to latest version, we ensure all the
packages depending on it continue to work by running tests (though it is
still a work in progress to enable tests in all packages because we have
not packaged all test frameworks) of all its reverse dependencies.

TODO: We have to package shelljs to enable tests in grunt, for gulp we
should be able to enable tests.

When a dependency is changed it triggers an autopkgtest of all its
reverse dependencies and we get notified of a test failure in

>> The last comment about obstructing it shows your intolerance towards
> users of your library. You can try, but if it is Free Software, we'll
> find a way.
> You're free to use the software under the terms of its license. I'm also
> free to not agree with your approach. It's not super great.

I was commenting about "I may take steps to obstruct this kind of thing
in future releases", that is not in the spirit of the license, it goes
beyond disagreement. The terms of the license allow me to flatten the

Attachment: signature.asc
Description: OpenPGP digital signature

Pkg-javascript-devel mailing list

Reply via email to