I'm not sure what you mean by a "regular" package manager. If you mean the package manager provided by a Linux distribution like Linux Mint or Manjaro, then yes, you can use that if you prefer.
However, creating packages that are Debian based (not sure how to create packages for Manjaro) takes a lot more work than simply adding a package.json file to your project. It's similar to spirit to using npm when creating/working on JS projects.
Yes, it's a bit harder to package for Debian, but it's a one-time job, and you don't have to edit anything related to the packaging pipeline to add or remove files, as it's completely independent of one's build tools.
That is true, but CLibs is focused on small C libraries; typically no more than a few files. So, adding/removing files from the package.json is not a frequent issue.
If your library is much bigger than a few files, that I would recommend going with a regular package manager.
Small libraries are lightweight because of their small footprint. You're only using what you need and not having it coupled with a framework or part of a bigger library.
Of course, bigger libraries have their place in the world of programming, but sometimes one just needs a micro library to do the job.
A couple of reasons: the creator of CLibs states that libraries for C are scattered all over the web and CLibs can help them discover these types of libraries for themselves.
CLibs isn't required to be installed for the end users or contributors. This allows CLibs to seamlessly integrate with any new or existing projects.
The author the library expressed the sentiment that the discovery of C libraries is "relatively poor" and sometimes they are unfocused and have a bigger than necessary footprint.
The point of CLibs is to use micro-libraries that meet your project's needs. Yes, a simple Google search might suffice for a bigger project, but for the search of smaller libraries, it might not.
Personally, I don't use CLibs, mainly because I only have one project in C. The reason I made this post is so that other people would know about and perhaps some of them would find a use for it.
Not to be mean or harsh, but can’t one just use a regular package manager?
I'm not sure what you mean by a "regular" package manager. If you mean the package manager provided by a Linux distribution like Linux Mint or Manjaro, then yes, you can use that if you prefer.
However, creating packages that are Debian based (not sure how to create packages for Manjaro) takes a lot more work than simply adding a package.json file to your project. It's similar to spirit to using npm when creating/working on JS projects.
Yes, it's a bit harder to package for Debian, but it's a one-time job, and you don't have to edit anything related to the packaging pipeline to add or remove files, as it's completely independent of one's build tools.
That is true, but CLibs is focused on small C libraries; typically no more than a few files. So, adding/removing files from the package.json is not a frequent issue.
If your library is much bigger than a few files, that I would recommend going with a regular package manager.
But then what’s the advantage with small libraries?
Small libraries are lightweight because of their small footprint. You're only using what you need and not having it coupled with a framework or part of a bigger library.
Of course, bigger libraries have their place in the world of programming, but sometimes one just needs a micro library to do the job.
No, I meant what advantage does one get by having people install one’s package through CLibs?
A couple of reasons: the creator of CLibs states that libraries for C are scattered all over the web and CLibs can help them discover these types of libraries for themselves.
CLibs isn't required to be installed for the end users or contributors. This allows CLibs to seamlessly integrate with any new or existing projects.
And how does it help people discover libraries any more than a simple Google search?
Again, CLibs helps to discover micro-libraries.
You didn’t answer my question.
The author the library expressed the sentiment that the discovery of C libraries is "relatively poor" and sometimes they are unfocused and have a bigger than necessary footprint.
The point of CLibs is to use micro-libraries that meet your project's needs. Yes, a simple Google search might suffice for a bigger project, but for the search of smaller libraries, it might not.
Personally, I don't use CLibs, mainly because I only have one project in C. The reason I made this post is so that other people would know about and perhaps some of them would find a use for it.
Still, what does it do to make discovery easier?
Just by using
clib search [package-name]. Sure, you could Google search it, but, it might not come up.But you still need to know about the library to do that, so it’s more of a “Can I install this through CLibs?” thing.
Sure. If you want to, Google can be a great place to find certain libraries and for others, it might not be.
There's nothing wrong with wanting to use Google for this purpose, it's just that CLibs can offer another channel for finding useful libraries.
Now you’re basically just repeating yourself.
Sorry, but that's all I have to say in this discussion. Use Google if you want and CLibs for an extra avenue for finding libraries.