| 1 |
вт, 6 окт. 2020 г. в 15:04, Marek Szuba <marecki@g.o>: |
| 2 |
> |
| 3 |
> On 2020-10-05 23:17, Azamat Hackimov wrote: |
| 4 |
> |
| 5 |
> >>> Is there a slotmove that can be applied? |
| 6 |
> >> |
| 7 |
> >> I am afraid I do not understand the question. What do you want to move, |
| 8 |
> >> and why? |
| 9 |
> > |
| 10 |
> > Currently portage is mostly lua:5.1 aware and the first thing is move |
| 11 |
> > dev-lang/lua:0 to 5.1 slot by slotmove in profiles/updates: |
| 12 |
> > |
| 13 |
> > slotmove dev-lang/lua 0 5.1 |
| 14 |
> |
| 15 |
> The file structure of dev-lang/lua:0 differs from dev-lang/lua:5.x, |
| 16 |
> meaning that introducing such a slot move would require Lua eclasses to |
| 17 |
> treat lua5-1 differently from other targets. In other words, we would |
| 18 |
> *still* need lua0 support but without a clearly distinct name. |
| 19 |
|
| 20 |
So there will be a new stabilized lua:5.1 version as I proposed. |
| 21 |
Again, here is a quick todo list: |
| 22 |
|
| 23 |
1. slotmove dev-lang/lua |
| 24 |
2. Change all dependencies to change from lua:0 to lua:5.1 |
| 25 |
3. Stabilize & unmask slotted version 5.1.5-r103 |
| 26 |
4. Release news & rebuild with emerge -a --oneshot $(equery depends |
| 27 |
dev-lang/lua | awk '{print " ="$1}') |
| 28 |
5. Now we have lua:5.1 portage ready to lua.eclass migration |
| 29 |
6. PROFIT |
| 30 |
|
| 31 |
1-4 can be done with one git push |
| 32 |
|
| 33 |
-- |
| 34 |
From Siberia with Love! |
Archives