From owner-freebsd-ports@freebsd.org Thu Jul 16 17:53:57 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B83009A358A for ; Thu, 16 Jul 2015 17:53:57 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7BD4514DD for ; Thu, 16 Jul 2015 17:53:57 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by oihq81 with SMTP id q81so55493109oih.2 for ; Thu, 16 Jul 2015 10:53:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XKcY7u08O6VecUJbHqlU93iykzYoUDaLv7zt+TI9xUY=; b=Atp3iU2lXEKw7hOnAqBB5hGRSte98ntL/PHl7YcN000h7G4/Qo7WNt7ltTSTcHmft2 gSRUjltxgQmpsO25yenqcQUQDBh2sDuBHU7L7HXmsdyCuINl7enstrw5xyVtb4idbHUY RmA/b7d+GiFmwYZdUYqQroX9Taq7NN0KYlyF7rhAEPmBENd77WBDY37Fke2EJwGz1jAI c1BGLo6ShJK8BcKgS9CR7+g9R5t6aLGCDsOfLdtBIYRfiZBkpgkvDsdeWb3FVjImr23N NsmKfRHn/ya0Qb0duI0MUaJ+O8ndGEPSIVfaD9Nvx/yaCqo45+6QHrByvJGN2C+qv7hh ytNA== MIME-Version: 1.0 X-Received: by 10.182.215.226 with SMTP id ol2mr9698455obc.56.1437069236717; Thu, 16 Jul 2015 10:53:56 -0700 (PDT) Received: by 10.76.81.100 with HTTP; Thu, 16 Jul 2015 10:53:56 -0700 (PDT) In-Reply-To: <55A7EE01.3080805@highsecure.ru> References: <55A7B826.2060609@citrin.ru> <55A7E877.3040802@highsecure.ru> <55A7EE01.3080805@highsecure.ru> Date: Thu, 16 Jul 2015 10:53:56 -0700 Message-ID: Subject: Re: port renaming From: Freddie Cash To: Vsevolod Stakhov Cc: Kimmo Paasiala , Henry Hu , "freebsd-ports@freebsd.org" , Anton Yuzhaninov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2015 17:53:57 -0000 On Thu, Jul 16, 2015 at 10:46 AM, Vsevolod Stakhov wrote: > On 16/07/2015 18:32, Kimmo Paasiala wrote: > > On Thu, Jul 16, 2015 at 8:23 PM, Vsevolod Stakhov > > wrote: > >> On 16/07/2015 18:11, Henry Hu wrote: > >>> > >>> > >>> On Thu, Jul 16, 2015 at 7:04 AM, Vsevolod Stakhov > >>> > wrote: > >>> > >>> On Thu, Jul 16, 2015 at 2:56 PM, Anton Yuzhaninov < > 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