A name colission with `soymuchacho/libshared`

[sskras]

I thought about making this project a standalone lib.
This happened after I saw both Task Warrior and Timewarrior use the same library and that I am building it twice.

And googled this name and I found another project of the same name (born at the similar time, Jul 16, 2016):
https://github.com/soymuchacho/libshared

Would it be acceptable for this project to adjust the name? Just a thought.

[smemsh]

Probably doesn't make sense to use a DSO that isn't linked statically. Taskwarrior/timewarrior have specific versions of libshared that they peg to (ie using git submodules) and the projects operate with different release schedules. In any case, libshared is probably only useful to the TW projects, and not a general purpose library, so a name collision isn't really problematic.

[sskras]

Fair enough.
I just don't get: why should I build libshared twice? Can't it be shared between these two projects in some other way?

[smemsh]

You don't need to build libshared yourself, the build system does it, so it's not any more effort is it? Do you mean because you have to init the submodules?

[sskras]

Initting modules might be a reason too, although a weaker one.
My primary concern is compilation of slow machines, where the same compilation work has to be done twice.

[tbabej]

I see where you're coming from, unfortunately, it's not exactly the same compilation work, because both timewarrior and taskwarrior often pin down different versions of libshared at any given point in time.

In case they are poining to the same commit in the submodule, you could circumvent the double build requirement by symlinking libshared from one repository into another 🤔

[sskras]

Ah, thanks for the tip! I guess I am fine with that then.

Still no plans to change the library name to something more specific?=)

[smemsh]

Still no plans to change the library name to something more specific?=)

is it used somewhere outside the context of the GothenburgBitFactory programs' linktime namespaces, such that it's even possible to collide with anything?