Re: Json-c library installed into /lib/ instead of /usr/lib/ ... is that relevant anymore?
- Date: Tue, 15 Jan 2019 23:47:21 +0100
- From: Marco d'Itri <md@xxxxxxxx>
- Subject: Re: Json-c library installed into /lib/ instead of /usr/lib/ ... is that relevant anymore?
On Jan 15, Boyuan Yang <byang@xxxxxxxxxx> wrote: > I digged a little bit into it and found out that it was originally due to > upstart that needed it during bootup  so the lib should be placed into /lib > according to FHS. However, with upstart disappeared from Debian archive (since > 2016), other init systems seem not having dependency on json-c and that > usrmerge is approaching, I'm wondering if we should move the installation path > back to /usr/lib. Will there be any side effects? Please do. Nowadays /usr/ is always available at early boot anyway. -- ciao, Marco
Description: PGP signature
- Prev by Date: Bug#919441: ITP: pyshacl -- A pure Python packages which allows for the validation of RDF graphs against Shapes Constraint Language (SHACL) files.
- Next by Date: Re: Handling of entropy during boot
- Previous by thread: Re: Json-c library installed into /lib/ instead of /usr/lib/ ... is that relevant anymore?
- Next by thread: Bug#919440: ITP: owlrl -- A simple implementation of the OWL2 RL Profile on top of RDFLib: it expands the graph with all possible triples that RDFS and OWL-RL defines. It can be used together with RDFLib to expand an RDFLib Graph object, or as a stand alone service with its own serialization.