[PATCH 0/2] split libosmocore library (to create libosmo-gsm)

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Pablo Neira Ayuso pablo at gnumonks.org
Sat Mar 19 19:44:29 UTC 2011


Hi Harald,

On 18/03/11 12:58, Harald Welte wrote:
> On Thu, Mar 17, 2011 at 10:08:47PM +0100, Sylvain Munaut wrote:
>>> 1) First, make a copy of libosmocore.git to libosmo-gsm.git. This is
>>> done to avoid losing the history in the new libosmo-gsm.git library.
>>
>> Can't this be made with git filter-branch somehow ?
> 
> I think we might just build libosmo-gsm as part of the libosmocore.git
> repository, similar to what we do for libosmovty.  But this may be
> a matter of personal taste ;)
> 
> What do others  think about it?  I think splitting the include paths
> and the .so file names makes users (i.e. the application programs)
> aware that it is two libraries.
> 
> Splitting the git repositories doesn'nt really buy us anything apart
> from yet another git checkout/update/configure/make/... that needs to be
> executed.

The only compelling argument that I can find to support the split are
releases. You can make release of the two libraries independently, in
case that this is one critical bug in one of the part.

However, I agree that we can do this in the future.

> If at some future point we want to split the repositories, it will not
> incur any changes to the application programs like openbsc, as they
> already check for two different pkgconfig etc.

I'll resend the patches with this new approach, putting all GSM-specific
stuff under a directory called libgsm inside libosmocore.

I can send patches to rename vty to libvty, and codec to libcodec (for
consistency with the naming approach in openbsc) if you like the idea.




More information about the OpenBSC mailing list