On Fri, Jun 23, 2017 at 10:40:25AM +0200, Vít Ondruch wrote:
>
>
> Dne 22.6.2017 v 17:15 Petr Šabata napsal(a):
> > While playing with Base Runtime container base images we noticed
> > that some packages couldn't be installed with coreutils-single
> > due to their /bin file dependencies. Unlike the original
> > coreutils package, coreutils-single doesn't provide the
> > pre-UsrMove paths.
> >
> > Now there are at least two ways to resolve this. We either
> >
> > a) change all the packages that depend on /bin/* coreutils
> > paths, or
> > b) we add the respective /bin provides to coreutils-single.
> >
> > Reading the packaging guidelines[0], I'd lean towards "fixing"
> > the coreutils subpackage, while the coreutils maintainers
> > believe we should change packages that depend on obsolete paths.
> >
> > For the record, there appear to be only 25 binary packages that
> > depend on /bin coreutils paths[1];
>
> What is the source of this /bin dependencies? Are they autogenerated or
> maintainers are using R: /bin/someutil (where they should be using
> %{_bindir}/someutil)?
>
>
> Vít
My first and incorrect query revealed hundreds of packages
which made me think it was probably generated. Kamil pointed
out that were it the case, we could just fix the generator.
But given the actual number of packages is this low, they were
probably explicitly added by their maintainers. The few I
checked were like that, at least.
P
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
