OK thanks, I will close this PR and create 2 PRs: one for kmini and another for
kpcre
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #901.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/901#event-922281331___
sr-dev mailing list
sr-dev@lists.sip-router.org
Yes, it's ok to add new groups that can help in what you need.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
buildroot does not use deb or rpm specs from kamailio tree.
To integrate a package to buildroot, I have to define a .mk that explain how to
download the source from github and selects the appropriate modules depending
on what packages were selected by the user.
For example, if the package
@ffontaine - is the buildroot using deb or rpm specs from kamailio tree?
There is another set of groups, which doesn't have 'k' as prefix of the last
word in the name -- for example, there is module_group_standard and
module_group_kstandard. The module_group_k... were intended for packaging,
My goal was to integrate kamailio into buildroot (https://buildroot.org/).
buildroot allows the user to create its own embedded linux system and the pcre
package is not always selected by the user.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
I do believe pcre is quite common and we can live with it on kstandard
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Maybe @linuxmaniac can have an additional opinion on this topic. There is a
conflict already due to other changes, so cannot be just merged any longer, but
the question of this PR is whether to to create or not a pcre group.
--
You are receiving this because you are subscribed to this thread.
I think this was added because of lcr module to be included in the main package
(e.g., deb) and pcre being very common.
If many people want to change this and have a dedicated group, then comment
here.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
Previously pcre was included into kstandard but pcre module depends on
pcre library so create its own group and remove it from kstandard as
standard modules should have no internal/external compile or link
dependencies
Signed-off-by: Fabrice Fontaine
You can view,
10 matches
Mail list logo