On 14500 March 1977, Michael Prokop wrote:
>> > Overall, I'm not sure we are providing our users something good with
>> > the current situation. Though what realistic options do we have get
>> > forward here? Any thoughts?
It neither helps Users nor Debian.
>> Most, if not all, npm dependencies
On 14501 March 1977, Jérémy Lal wrote:
>> - This is not a blanket for having embedded code copies all over the
>>place.
>>So yes, this should Provide: all those submodules and make them
>>usable by whoever depends on it.
>> - This must be rebuildable in Debian. That is, the package
On 14501 March 1977, Jérémy Lal wrote:
>> - If upstream deicdes to remove one of the bundled libs, which you have
>>a provides for - and that provides is used in debian (has rdepends),
>>you just earned a new package to maintain.
> Unless no other package depends on it ?
Yeah sure,
On 14963 March 1977, Pirate Praveen wrote:
> 1. If a single ftp master is in disagreement, there should be a team
> decision (in previous cases of disagreement also, other team members did
> not get involved).
I wonder why you think "a single ftpmaster". We are a team. We closely
coordinate what
On 14963 March 1977, Pirate Praveen wrote:
>> I wonder why you think "a single ftpmaster". We are a team. We closely
>> coordinate what we do and how we do it. When one of us rejects, the team
>> rejects - it just happens to be a random one of us doing it. Others do
>> not need to get involved
On 14959 March 1977, Pirate Praveen wrote:
8 node modules (all of them dependencies of gitlab) depend on this
module (colormin, cssnano, eslint-import-resolver-webpack,
eslint-plugin-import, postcss-merge-idents, postcss-minify-selectors,
postcss-reduce-transforms,
