Date: Thu, 16 Jul 2015 10:53:56 -0700 From: Freddie Cash <fjwcash@gmail.com> To: Vsevolod Stakhov <vsevolod@highsecure.ru> Cc: Kimmo Paasiala <kpaasial@gmail.com>, Henry Hu <henry.hu.sh@gmail.com>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>, Anton Yuzhaninov <citrin@citrin.ru> Subject: Re: port renaming Message-ID: <CAOjFWZ5c5hGfWuJNfTXmP9=rXP%2B9rzL6TvVj4=%2BhcW3MPokpvg@mail.gmail.com> In-Reply-To: <55A7EE01.3080805@highsecure.ru> References: <55A7B826.2060609@citrin.ru> <CAFb6gngdDLLDiQU%2BwmYE17zmuo3YU=_e_7ruvDVufxGmQuk1=A@mail.gmail.com> <CAEJt7haPtdqbH8RPAYZaMY43F0doN7xtr%2Bz94xv-89rz9%2BzcXQ@mail.gmail.com> <55A7E877.3040802@highsecure.ru> <CA%2B7WWSerx%2BgWSN0wBg%2BLPfSOu4A=LDZYX1Kn-5hwkY1svnUUpA@mail.gmail.com> <55A7EE01.3080805@highsecure.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 16, 2015 at 10:46 AM, Vsevolod Stakhov <vsevolod@highsecure.ru> wrote: > On 16/07/2015 18:32, Kimmo Paasiala wrote: > > On Thu, Jul 16, 2015 at 8:23 PM, Vsevolod Stakhov > > <vsevolod@highsecure.ru> wrote: > >> On 16/07/2015 18:11, Henry Hu wrote: > >>> > >>> > >>> On Thu, Jul 16, 2015 at 7:04 AM, Vsevolod Stakhov > >>> <vsevolod@highsecure.ru <mailto:vsevolod@highsecure.ru>> wrote: > >>> > >>> On Thu, Jul 16, 2015 at 2:56 PM, Anton Yuzhaninov < > citrin@citrin.ru > >>> <mailto:citrin@citrin.ru>> wrote: > >>> > > >>> > Port maintainers and port commiters, when > PORTNAME/PKGNAMEPREFIX/PKGNAMESUFFIX is changed, please note this change = in > commit log and for important ports also in /usr/ports/UPDATING. Any renam= e > affect at leas some of FreeBSD users and > >>> > > >>> > Depends in our local ports was broken and I spent some time to > figure out why. > >>> > It turns out, that PORTNAME for graphics/gd was changed in > r324437. > >>> > No singe word about this rename was added to commit message or > UPDATING... > >>> > >>> From the perspective of pkg things are even worse, as pkg can no > >>> longer detect that the renamed package is a replacement for some > >>> existing one. It breaks many stuff and solver could hardly help t= o > >>> resolve this in a pain-less matter. We need something like > 'Replace' > >>> or 'Obsolete' field badly. 'UPDATING' does NOT help to solve this > task > >>> at all. > >>> > >>> > >>> We already have the 'MOVED' file. Does it help? > >> > >> It doesn't because: > >> > >> 1) it is human readable and not very convenient for parsing; > >> 2) we must keep this information on per-package basis and not globally= ; > >> 3) many items are missing in MOVED (and I've recently missed one when > >> changing a port, for example) > >> 4) MOVED contains too many unnecessary information that is useful mere= ly > >> because we are using archaic version control system (namely, subversio= n) > >> > >> So the answer is no: we need a special field in manifests to make > >> renaming transparent for pkg and, in turn, for users. > >> > >> -- > >> Vsevolod Stakhov > > > > > > So basically you need a data structure in the pkg metadata that can > > track all the previous origins for the port (not just the last because > > ports might have multiple renames). That's quite a tall order I might > > say. > > Why? We have already arrays in a package's metadata. For instance, > licenses or dependencies. And we can obviously avoid that by placing a > corresponding field 'Obsoleted by' in the *old* package. Then we'd need > merely the last rename. > =E2=80=8BOr a "Replaces:" field in the new package, similar to how Debian p= ackages work.=E2=80=8B --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ5c5hGfWuJNfTXmP9=rXP%2B9rzL6TvVj4=%2BhcW3MPokpvg>