Hello Federico, In git master we should have the -9999 file, and in the respective stable branches the other files.
You can send me the files e.g. as zip or patch file directly (send not to the list), and I integrate it in the repository. You could do further updates then directly there. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Federico Santulli <[email protected]> Sent: Thursday, February 13, 2020 3:54 PM To: Henning Westerholt <[email protected]> Cc: Kamailio (SER) - Development Mailing List <[email protected]> Subject: Re: [sr-dev] About FOSDEM talks Hi Henning, actually i’m going to pull the pkg/kamailio/gentoo folder. It contains: · files o kamailio.confd o kamailio.initd · kamailio-5.1.10.ebuild · kamailio-5.2.6.ebuild · kamailio-5.3.2.ebuild · kamailio-9999.ebuild As it contains all builds for every single version, and also the one for the master release, how you think they should be packaged? One ebuild for every release and the 9999 for the master or all in one? Could be the commit message like this? pkg/gentoo: Added ebuild for versions 5.1.10, 5.2.6, 5.3.2 and master. Please let me know. Best regards. Federico Santulli NHM - S.R.L. Via Raffaello Sanzio, 88 81031 Aversa (CE) Italy Il giorno 13 feb 2020, alle ore 13:53, Henning Westerholt <[email protected]<mailto:[email protected]>> ha scritto: Hello Federico, Great to hear from you, it was nice to meet you at FOSDEM! Extensions to modules that add new useful functionality are always welcome, and packaging support of course as well. You probably know this document already, it gives many hints about our way of working and some guidelines for commit messages etc.. https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md The usual way how we work in Kamailio is to use github pull requests. So the best way would be if you create pull requests for the sdpops extensions and the gentoo ebuild. For the historyinfo header extensions I think a pull request would be good as well. In this case we should discuss with the other developers in the request how to merge it best, e.g. as a dedicated module or to add them to the pv module, for example. If you plan to do more work on the Gentoo ebuild packaging, you will get also commit access to our repository that you can maintain the ebuild files directly in git master. Just let us know after you submitted the first Gentoo packaging pull request. The old ebuilds were removed because they were outdated. One last note - new functionality will be included in the next major release 5.4.0, the package files can be also integrated into the stabled releases branches 5.3 and 5.2. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com -----Original Message----- From: sr-dev <[email protected]<mailto:[email protected]>> On Behalf Of Federico Santulli Sent: Thursday, February 13, 2020 12:57 PM To: [email protected]<mailto:[email protected]> Subject: [sr-dev] About FOSDEM talks Hi Henning, as I was discussing with you at the fosdem dinner we were developing something on the 5.3 branch yet: we have a module for the history info processing with functions and pv variables $hi[index] handling. As I told you before moving the pvs to the core, we would like to have a well tested module. We have also added functions to the sdpops module to allow codec reorder, remove and other manipulations over the request/response processing (matching between invites and updates with 200 OK responses). We have added native and kemi functions to the userblacklist module where we do global filtering based on the from uri or other customer selected field. We have also readded and updated the Gentoo ebuilds that were removed many releases ago. We based them on the stable releases and we have one too for git with version 9999 as usual. Do you think we can start to push some code? Kind regards. Federico Santulli NHM - S.R.L. Via Raffaello Sanzio, 88 81031 Aversa (CE) Italy _______________________________________________ Kamailio (SER) - Development Mailing List [email protected]<mailto:[email protected]> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
_______________________________________________ Kamailio (SER) - Development Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
