| 1 |
On Sun, 19 Apr 2015 03:38:09 -0600 |
| 2 |
Ryan Hill <rhill@g.o> wrote: |
| 3 |
|
| 4 |
> On Wed, 8 Apr 2015 16:25:20 +0100 |
| 5 |
> James Le Cuirot <chewi@g.o> wrote: |
| 6 |
> |
| 7 |
> > On Wed, 8 Apr 2015 17:10:30 +0200 |
| 8 |
> > Patrice Clement <monsieurp@g.o> wrote: |
| 9 |
> > |
| 10 |
> > > Tuesday 07 Apr 2015 20:41:05, Pacho Ramos wrote : |
| 11 |
> > > > Wouldn't be possible to show a repoman warning when a |
| 12 |
> > > > dependency on any dev-java/${PN} doesn't specify a SLOT? That |
| 13 |
> > > > would save of from forgetting this in some years ;) |
| 14 |
> > > > |
| 15 |
> > > Chewi suggested a similar solution in #gentoo-java. How do we get |
| 16 |
> > > started with contributing to repoman? |
| 17 |
> > |
| 18 |
> > The change I intend to make is not to repoman but |
| 19 |
> > java-utils-2.eclass where there is already a check to ensure that a |
| 20 |
> > dependency has been added, it just doesn't check the SLOT at the |
| 21 |
> > moment. It outputs an error message by default but dies if you have |
| 22 |
> > JAVA_PKG_STRICT set, which all Java devs should do. |
| 23 |
> |
| 24 |
> I just got this warning and had to do some digging to figure out |
| 25 |
> where it came from and what it wanted me to do. Can you add a comment |
| 26 |
> to the eclass (maybe a link to your mail which explained things well) |
| 27 |
> and a pointer to the eclass in the message? |
| 28 |
|
| 29 |
Done! :) |
| 30 |
|
| 31 |
-- |
| 32 |
James Le Cuirot (chewi) |
| 33 |
Gentoo Linux Developer |
Archives