I just created a dub package. Frankly, the whole thign is backward.

[Steven Schveighoffer]

On 4/26/22 5:38 PM, deadalnix wrote:
> On Tuesday, 26 April 2022 at 19:29:31 UTC, Steven Schveighoffer wrote:
>> The solution is not to bring everyone down to your misery though. "If 
>> I can't have a good experience with what I want, nobody should" isn't 
>> the right answer.
> 
> I'm not bringing anyone anywhere. You want to use make? Good. 
> cmake/ninja? Good. Scons? Good. A custom build script? Good.
> 
> I really don't what you use.
> 
> I *DO* care about dub because dub doesn't provide me with a good way to 
> work with it without dubifying everything.

I'm perfectly fine with projects not using dub. Don't listen to people 
who cry about dub usage.

> See I lead a project that uses cmake/ninja. It has dependencies using 
> autotools, cmake, qmake, and even some that uses their own thing. None 
> of that causes any significant problems.

And I lead projects that use dub. People have asked me to include meson 
build files in some cases. And I've obliged, but I hate maintaining it 
(most important reason -- meson build file must be manually updated to 
match git tag). I'd rather just get rid of them, and if you don't want 
to use dub to build my projects, then roll your own fork.

> 
> But dub don't just want to build the thing or do dependency management. 
> Dub is the true way to enlightenment. You have to do it all the dub way 
> or be in a world of pain.

Don't use dub, no enlightenment necessary.

> 
> All I'm asking is that you sub guy recognize for other the same thing as 
> you are now requesting for yourself: don't impose a way of doing things 
> on me because it is the one true way™.

I'm not. I said this from my first post on this unreasonably long 
thread, I don't care what you use, D does not require you to use dub to 
build.

-Steve