Date: Fri, 25 May 2012 07:46:37 -0400 From: "Dan Langille" <dan@langille.org> To: "Erwin Lansing" <erwin@FreeBSD.org> Cc: Max Brazhnikov <makc@freebsd.org>, cvs-ports@freebsd.org, Dan Langille <dan@langille.org>, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/archivers/ark Makefile distinfo pkg-descr pkg-plist ports/comms/kremotecontrol Makefile distinfo pkg-descr pkg-plist ports/deskutils/kcharselect Makefile distinfo pkg-descr pkg-plist ports/math/kcalc Makefile distinfo pkg-descr pkg-plist ... Message-ID: <1b0b3847f3bfd240ac2ccf10515cbaa4.squirrel@nyi.unixathome.org> In-Reply-To: <20120525064518.GW31494@droso.net> References: <201205242127.q4OLRuZY071969@repoman.freebsd.org> <F19A3712-9D9B-4D94-A920-FF145F1B4A2F@langille.org> <20120525064518.GW31494@droso.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 25, 2012 2:45 am, Erwin Lansing wrote: > On Thu, May 24, 2012 at 10:11:52PM -0400, Dan Langille wrote: >> When a port is repocopied, should the Makefile be altered to reflect the >> new location? >> >> For example, securty/kwallet/Makefile contains: >> >> CATEGORIES= misc kde >> >> I've seen this problem before, but I didn't write it in for >> http://news.freshports.org >> >> What I did was write a script to detect such situations. This is how it >> came to my attention. The ports in question are: >> > [snip] > >> > Log: >> > Forced commit to note repocopies: >> > > > Current best practice is to do a forced commit after the repocopy right > before updating the new port to whatever change its going to have > compared to its master. This is just so the reopocopy itself is > mentioned in the commitlogs as a workaround for cvs. You're right that > if the port moves category, its CATEGORIES, and thus ORIGIN, and > possibly other metainformation will be wrong between the forced commit > and the update commit. It's not ideal and hopefully it will all go away > when me move to subversion. I understand. From a FreshPorts point of view, the forced commit for the repo copy is great, as this is how FreshPorts learns of the move. The subsequent update commit should sort things out. Thank you. :) -- Dan Langille -- http://langille.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1b0b3847f3bfd240ac2ccf10515cbaa4.squirrel>