search

dbuenzli / topkg

The transitory OCaml software packager
http://erratique.ch/software/topkg
ISC License
69 stars 25 forks source link

Please break the cyclic build dependency #116

Closed infinity0 closed 7 years ago

infinity0 commented 7 years ago

Continuing from https://github.com/dbuenzli/topkg/issues/115#issuecomment-315915323

That's precisely what you don't understand. The cost is much lesser for me that way, I manage approximatively 30 OCaml packages and I need to be efficient in this (see here for more on this). With appropriate tooling on the debian side which is perfectly possible by using the opam v2 API on I don't think it will incur a cost there. [..] Maybe you should be a little bit more open minded and try to understand why things are done in a certain manner before starting yelling to much and "explain" me things and try to impose your viewpoint about things.

Maybe you should stop acting with such a bullshit superiority complex. You think you're not wasting my time? If you had explained to me details of your issues, instead of coming out with bullshit comments like "This seems rather a debian packaging mistake", "I challenged your intuitions", we could have had a proper conversation about the technical details of your concerns.

I maintain 44 Debian packages. Actually the true number is a bit more, one of them has about 180 build dependencies so in practise I have to deal with those too. Incidentally the sagemath guys were nice enough to listen to my points about cyclic build-dependencies, they had a similar issue last year which they fixed after I asked them to.

dbuenzli commented 7 years ago

As I suspected, the pleasantly unhysterical person in charge of packaging topkg downstream perfectly understands there is no circular dependency. See the discussion here and follow-ups.