On 05/06/14 11:58 , "Vitaly Chernooky" 
<[email protected]<mailto:[email protected]>> 
wrote:

Hi Alexander,


On Wed, Jun 4, 2014 at 7:20 PM, Kanevskiy, Alexander 
<[email protected]<mailto:[email protected]>> wrote:
On 04/06/14 18:29 , "Vitaly Chernooky" 
<[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>
 wrote:

Hi all,

How do you usually deal with cyclic dependency?

break it, refactor it. It really depends on each specific case.

It is not a generic question but about few well-known cyclic dependency 
especially in Tizen (3.0)


can you be a bit more specific please ?

And why it is not solved in common ways?

Usually those should not be created in proper designed modular software. :)
However reality is far from that, if there is opportunity to develop components 
independently using some “assumed” build dependencies – people do design 
mistakes and create cycles.

Before I had deal with many Linux-based distros, but Tizen is first where 
cyclic dependency was not solved on early stages.

Practically every Linux distro nowadays have multiple dependency cycles. In 
most of them, it is solved by different variants of implicit build dependencies.
E.g. in Debian/Ubuntu it is done via “build-essentials”, in Fedora it is 
'buildsys-build’ group and so on.

In Tizen 3.0 currently existing cycle is related to toolchain and build 
essentials as well: 
https://build.tizen.org/project/repository_state?project=Tizen%3ACommon&repository=ia32-wayland

--
Best regards, Alexander Kanevskiy.
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to