java-pkg_getjar lucene:2.3 lucene-core.jar This is a valid statement at compile time even if EAPI is not declared to be 1 but the env file entry is not translated into old notation and causes package not found error at runtime. Reproducible: Always Steps to Reproduce: 1. don't declare EAPI="1" in the ebuild 2. use slot notation in java-pkg_getjar 3. merge the package and run Actual Results: Fails to run with package not found error. Expected Results: I think this notation should not be allowed (die with error) at compile time at all.
Created attachment 151262 [details] atunes-1.8.3.ebuild Sample ebuild i was working on and hit the issue.
Created attachment 151264 [details] package.env package.env file generated.
(In reply to Serkan Kaba (RETIRED) from comment #0) > java-pkg_getjar lucene:2.3 lucene-core.jar > > This is a valid statement at compile time even if EAPI is not declared to be > 1 but the env file entry is not translated into old notation and causes > package not found error at runtime. > > Reproducible: Always > > Steps to Reproduce: > 1. don't declare EAPI="1" in the ebuild > 2. use slot notation in java-pkg_getjar > 3. merge the package and run > > Actual Results: > Fails to run with package not found error. > > Expected Results: > I think this notation should not be allowed (die with error) at compile time > at all. From what I gather, he hit the bug whilst not declaring an EAPI in his ebuild, which is bad. Fast forward 10 years and many RFCs and GLEPs have been written in the meantime which now forbid developers to commit ebuilds < EAPI version 5, let alone ebuilds with no EAPI declare). There's no way this bug will ever occur, ever again. Closing it.
