1 |
Dnia 2015-04-15, o godz. 22:27:03 |
2 |
James Le Cuirot <chewi@g.o> napisał(a): |
3 |
|
4 |
> On Sat, 11 Apr 2015 12:29:11 +0200 |
5 |
> "Andreas K. Huettel" <dilfridge@g.o> wrote: |
6 |
> |
7 |
> > > I felt the need to write the above because I have seen many |
8 |
> > > instances where devs not familiar with Java packaging have made |
9 |
> > > this mistake. Now I need to ask what to do in the case of ebuilds |
10 |
> > > that have already been marked stable. |
11 |
> > > |
12 |
> > > To bring up a real example, I would like to bump dev-java/jna with |
13 |
> > > a new SLOT for the new version. There are several reverse |
14 |
> > > dependencies, 3 of which do not specify a SLOT, and 2 of these have |
15 |
> > > already been marked stable. Upon giving jna a new SLOT, all these |
16 |
> > > packages would instantly fail to build if jna:0 is not already |
17 |
> > > installed and they would also fail to run if jna:0 gets depcleaned. |
18 |
> > > Simply leaving the stable ebuilds as they are is therefore not an |
19 |
> > > option. My preferred solution would be create a revbump that solely |
20 |
> > > amends (R)DEPEND, leaving the KEYWORDS exactly as they are. This is |
21 |
> > > controversial but what other choice is there? I could delay the jna |
22 |
> > > bump but this would push back this thread of work by a month when I |
23 |
> > > already have a huge backlog. Please do not let bureaucracy get in |
24 |
> > > the way here. |
25 |
> > |
26 |
> > Sounds good to me (as long as repoman agrees :). |
27 |
> |
28 |
> Turns out it doesn't agree. |
29 |
> |
30 |
> RepoMan scours the neighborhood... |
31 |
> KEYWORDS.stable [fatal] 1 |
32 |
> dev-embedded/arduino/arduino-1.0.5-r1.ebuild added with stable keywords: amd64 x86 |
33 |
> |
34 |
> What are my options? Force it? :/ |
35 |
|
36 |
portage-9999 has new -S (--straight-to-stable) option for repoman. |
37 |
|
38 |
-- |
39 |
Best regards, |
40 |
Michał Górny |