On 04/26/2013 02:25 PM, Matwey V. Kornilov wrote:

We are getting a lots of packages inside the devel:languages:erlang. We should think to change project structure to avoid massive rebuild of packages at erlang updates. My suggestion is to follow devel:langages:python approach: maintaince project for erlang is devel:languages:erlang:Factory, and packages inside devel:languages:erlang are built against erlang from the *distribution* repository (or from openSUSE:Factory for factory).

Makes sense to me. Even though currently Erlang on openSUSE is still in it's infancy, we're rapidly figuring things out. While we not only avoid massive rebuilds, we also avoid shadowing issues with released 'erlang' packages. In other words, if we do something incompatible in d:l:e, we want to see that. So thanks for bringing that up!

Since we can not just broke the things, the following roadmap is proposed:

1) move devel:languages:erlang/erlang to devel:languages:erlang:Factory/erlang and make a link from devel:languages:erlang:Factory/erlang to devel:languages:erlang/erlang. Change devel project for openSUSE:Factory/erlang to devel:languages:erlang:Factory.

2) disable devel:languages:erlang/erlang for Factory and upcoming openSUSE 13.1 in order to make erlang packages use erlang from the distribution. then disable for 13.2, 13.3, etc. At this step for openSUSE >= 13.1 packages from the project will use erlang from distribution, and the packages for openSUSE < 13.1 will use erlang from devel:languages:erlang, as they do now.

3) when all versions up to 12.3 will be discontinued, drop disabled devel:languages:erlang/erlang finally.

I would rather drop 'erlang' from d:l:e altogether to avoid confusion. You can add a repository path to the openSUSE_13.1 build target instead. 12.2 and 12.3 already ship erlang, thus need none in d:l:e, same as Factory btw. In other words, the project _meta could look like the following: ... <repository name="openSUSE_12.1"> <path project="devel:languages:erlang:Factory" <path project="openSUSE:12.1" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> ... <repository name="bleeding_edge_erlang_Factory"> <path project="devel:languages:erlang:Factory" repository="openSUSE_Factory"/> <arch>i586</arch> <arch>x86_64</arch> </repository> ... This is how we do it in devel:languages:python by the way. And that reminds me that I should probably do something similar in devel:languages:go :-) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hi, On Fri, 26 Apr 2013 16:25:01 +0400 "Matwey V. Kornilov" <matwey.kornilov@gmail.com> wrote:

My suggestion is to follow devel:langages:python approach: maintaince project for erlang is devel:languages:erlang:Factory, and packages inside devel:languages:erlang are built against erlang from the *distribution* repository (or from openSUSE:Factory for factory).

Fine for me. Regards, Nanuk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org