We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it a good idea to make pkgutil.{cpp,h} as external library? Something like libpkgutil.{so,a}. Should we keep these files in the pkgutils project?
pkgutil.{cpp,h}
libpkgutil.{so,a}
pkgutils
There are not so many lines of code:
$ wc -l pkgutil.* 1109 pkgutil.cpp 120 pkgutil.h 1229 total
We can provide dynamic and static linking support and make an availability not only to pkg{add,info,rm} to link against it, but to pkgman too.
pkg{add,info,rm}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is it a good idea to make
pkgutil.{cpp,h}
as external library? Something likelibpkgutil.{so,a}
. Should we keep these files in thepkgutils
project?There are not so many lines of code:
We can provide dynamic and static linking support and make an availability not only to
pkg{add,info,rm}
to link against it, but to pkgman too.The text was updated successfully, but these errors were encountered: