This library may be private however this does not mean it should be hidden in a dedicated path. But I guess its better to lower qa guards then carry a patch for life
On Dec 13, 2016 7:20 AM, "Mark Asselstine" <[email protected]> wrote: On Monday, December 12, 2016 9:17:14 PM EST Burton, Ross wrote: > On 12 December 2016 at 20:51, Mark Asselstine < [email protected] > > wrote: > > > > I think the discussion I pointed to in the commit log closes the door on > > any > > such change. Specific the comment from Lennart -- > > https://github.com/systemd/systemd/issues/3810#issuecomment-235290526 > > > > They don't want the library to be found in the default search path, they > > want > > to maintain this as a "hidden, internal resource". > > Oh if it's an implementation detail of systemd and not a user-facing > library then I can see their argument I guess. > > Don't agree with it though. But, the point is that as long as the parts of > systemd that could realistically be multilibd are in $libdir then this > isn't a problem. It is definitely an internal infra item for systemd and not seen as a 'public' library so I think we are best to run with it. I am with you that I don't necessarily agree with it. Khem, does this satisfy your concerns? Mark > > Ross
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
