Re: Best practice for dub registry package and module names

2022-09-06 Thread Vijay Nayar via Digitalmars-d-learn
On Sunday, 4 September 2022 at 01:52:11 UTC, Ali Çehreli wrote: Let's say I have three modules that work together, which I want to register on dub: A, B, and C. Here I would take inspiration from the Java world, where a "domain" is used per project. Typically this domain is written from the

Re: Best practice for dub registry package and module names

2022-09-04 Thread Adam D Ruppe via Digitalmars-d-learn
On Sunday, 4 September 2022 at 03:50:56 UTC, Ali Çehreli wrote: For example, there is fixedsizearray, which does not belong to any package: Yeah, this is bad design since two separate people might reuse the name and then end users - even if it comes through a couple layers of dependencies the

Re: Best practice for dub registry package and module names

2022-09-04 Thread Adam D Ruppe via Digitalmars-d-learn
On Sunday, 4 September 2022 at 01:52:11 UTC, Ali Çehreli wrote: Should the package be the author's name: acehreli.a, acehreli.b, and acehreli.c? This is what I'd suggest. You want something that nobody else is likely to step on throughout the entirety of the D ecosystem. It doesn't have to li

Re: Best practice for dub registry package and module names

2022-09-03 Thread Mathias LANG via Digitalmars-d-learn
On Sunday, 4 September 2022 at 01:52:11 UTC, Ali Çehreli wrote: Should the package be the author's name: acehreli.a, acehreli.b, and acehreli.c? I use this approach: https://forum.dlang.org/thread/jdkmtgftmwtwaxxqh...@forum.dlang.org

Re: Best practice for dub registry package and module names

2022-09-03 Thread rikki cattermole via Digitalmars-d-learn
I cannot recommend looking at how Adam has done it. I've been trying to get him to change it since he originally did it. It has known issues and yes it will still pull in all modules thanks to -I behavior except you get fun things like linker errors. Keep in mind, you are trying to optimize

Re: Best practice for dub registry package and module names

2022-09-03 Thread Ali Çehreli via Digitalmars-d-learn
On 9/3/22 20:39, Ali Çehreli wrote: For example, there is fixedsizearray, which does not belong to any package: https://code.dlang.org/packages/fixedsizearray On the other hand, arsd-official:minigui does have a package. (And that answers a question: Dash character is acceptable in package a

Re: Best practice for dub registry package and module names

2022-09-03 Thread rikki cattermole via Digitalmars-d-learn
Yeah you're over thinking this. It is a single dub package with a namespacing package directory.

Re: Best practice for dub registry package and module names

2022-09-03 Thread Ali Çehreli via Digitalmars-d-learn
On 9/3/22 20:04, rikki cattermole wrote: > This slightly smells, single module dub packages. > > What does each module do? The other issue is NIH because some of their functionality already exists. :/ A: Block of elements B: Expanding circular buffer C: Cache of elements I would like to reg

Re: Best practice for dub registry package and module names

2022-09-03 Thread zjh via Digitalmars-d-learn
On Sunday, 4 September 2022 at 01:52:11 UTC, Ali Çehreli wrote: Let's say I have three modules that work together, which I want to register on dub: A, B, and C. You should learn `ARSD`, and become `Ali-official`.

Re: Best practice for dub registry package and module names

2022-09-03 Thread rikki cattermole via Digitalmars-d-learn
This slightly smells, single module dub packages. What does each module do?

Best practice for dub registry package and module names

2022-09-03 Thread Ali Çehreli via Digitalmars-d-learn
Let's say I have three modules that work together, which I want to register on dub: A, B, and C. Although the most interesting one is C and A and B are used in its implementation, A and B can be registered individually as well and be used as C's dependencies. I know package-less modules are

dub-registry

2022-08-12 Thread Ruby The Roobster via Digitalmars-d-learn
I am currently trying to set up for myself a personal dub registry, and I have MongoDB installed. Yet, when I run `dub run` in the repo directory, I get the following error message: ``` vibe.db.mongo.connection.MongoAuthException@C:\Users\User\AppData\Local\dub\packages\vibe-d-0.9.4\vibe-d

DUB Registry

2020-05-15 Thread Luis via Digitalmars-d-learn
There is a way to make to ignore some branchs and tags? Actually it's pretty annoying when someone publish a fork, and spams with "does not match the original package name" on older tags.

Re: Need advice on using DUB registry

2017-04-02 Thread drug via Digitalmars-d-learn
02.04.2017 17:43, Eric пишет: On Sunday, 2 April 2017 at 04:14:56 UTC, rikki cattermole wrote: On 02/04/2017 2:37 AM, Eric wrote: I'm planning on some day putting a package in the DUB registry. My package is dependent on my "util" package which is a collection of stuff I us

Re: Need advice on using DUB registry

2017-04-02 Thread Eric via Digitalmars-d-learn
On Sunday, 2 April 2017 at 04:14:56 UTC, rikki cattermole wrote: On 02/04/2017 2:37 AM, Eric wrote: I'm planning on some day putting a package in the DUB registry. My package is dependent on my "util" package which is a collection of stuff I use across all my projects. D

Re: Need advice on using DUB registry

2017-04-01 Thread rikki cattermole via Digitalmars-d-learn
On 02/04/2017 2:37 AM, Eric wrote: I'm planning on some day putting a package in the DUB registry. My package is dependent on my "util" package which is a collection of stuff I use across all my projects. Does this mean I also have to put my util package in the DUB registry? Co

Need advice on using DUB registry

2017-04-01 Thread Eric via Digitalmars-d-learn
I'm planning on some day putting a package in the DUB registry. My package is dependent on my "util" package which is a collection of stuff I use across all my projects. Does this mean I also have to put my util package in the DUB registry? Could I just make "util"