Provides section

[radekg]

Hi there, great project, so it seems. Just one thing I am wondering though: any reason why the Provides are not set? Say I have a package which depends on java-runtime-headless, if I install openjdk from the result of the build of this project:

root@647262d44332:/tmp# grep-status -FProvides,Package -sPackage,Provides,Status java-runtime-headless
root@647262d44332:/tmp#

Installing openjdk-8-jdk from openjdk-r/ppa, the same command:

root@647262d44332:/tmp# grep-status -FProvides,Package -sPackage,Provides,Status java-runtime-headless
Package: openjdk-8-jre-headless
Provides: java-runtime-headless, java2-runtime-headless, java5-runtime-headless, java6-runtime-headless, java7-runtime-headless, java8-runtime-headless
Status: install ok installed

[hgomez]

DEB or RPM ?

[radekg]

DEB, sorry, should've mention...

[hgomez]

ok.

For DEB, I use FPM as I'm not a DEB packager specialist.

I guess We should add --provides

PR welcomed

[radekg]

I see if I could do a pr...

[hgomez]

BTW, take care

Obuildfactory JDK is not deployed on system location (/usr/...) as it's more an alternative Java Environment for tests purposes and to avoid collisions with distro Java packages.

So defined provides may cause problems, if an app expect Java Env ready to use but didn't find it in PATH

[radekg]

Yeah, I noticed, would you mind a configurable (with an env variable) output directory?

[hgomez]

If configurable is to have a 'system' wide mode, it would requires more works, for example alternatives use, which is not the target for Obuildfactory packages

[radekg]

Ok, let's skip alternatives. I can do with linking and setting JAVA_HOME. However, Provides is the minimum. Does that sound ok?

[hgomez]

Provides is ok yes :)

[hgomez]

PR ?

[hgomez]

No PR, closing ticket