| 1 |
On Saturday 19 March 2005 16:55, Jason Stubbs wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> Too frustrated to bother with a big explanation right now... |
| 5 |
> |
| 6 |
> Q1-2005 has the following number of packages pointing to a single package: |
| 7 |
> |
| 8 |
> 19 -> kde-base/kate-plugins |
| 9 |
> 7 -> kde-base/kdeaddons-kfile-plugins |
| 10 |
> 3 -> kde-base/kdebase-data |
| 11 |
> 2 -> kde-base/kdenetwork |
| 12 |
> 3 -> kde-base/kdewebdev |
| 13 |
> 6 -> kde-base/kicker-applets |
| 14 |
> 19 -> kde-base/konq-plugins |
| 15 |
> 15 -> kde-base/noatun-plugins |
| 16 |
> |
| 17 |
> "MOVE" != "MERGE" |
| 18 |
> |
| 19 |
> Buy a dictionary. |
| 20 |
Well we also put in blocking deps etc. Aside from that what's the correct |
| 21 |
procedure here, if not to use move instructions? |
| 22 |
It's true that the file list won't match. For which reason the target package |
| 23 |
always started out at a greater version than what was available for any |
| 24 |
source package. So after the move, the next world update should re-merge the |
| 25 |
correct, complete package. |
| 26 |
|
| 27 |
Yes this is ugly. But we only did it for package.masked ebuilds... What's a |
| 28 |
better way? |
| 29 |
|
| 30 |
-- |
| 31 |
Dan Armak |
| 32 |
Gentoo Linux developer (KDE) |
| 33 |
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key |
| 34 |
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951 |
Archives