Date: Mon, 16 Apr 2007 21:59:02 +0200 From: Dejan Lesjak <dejan.lesjak@ijs.si> To: Kris Kennaway <kris@obsecurity.org> Cc: x11@freebsd.org, Florent Thoumie <flz@freebsd.org> Subject: Re: Upgrade script Message-ID: <200704162159.02888.dejan.lesjak@ijs.si> In-Reply-To: <20070416193542.GA66481@xor.obsecurity.org> References: <20070414194028.GB2313@xor.obsecurity.org> <4623CA92.3020907@FreeBSD.org> <20070416193542.GA66481@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 16 April 2007 21:35:42 Kris Kennaway wrote: > On Mon, Apr 16, 2007 at 08:12:18PM +0100, Florent Thoumie wrote: > > Kris Kennaway wrote: > > > On Mon, Apr 16, 2007 at 01:35:08PM +0200, Dejan Lesjak wrote: > > >> On Monday 16 of April 2007, Kris Kennaway wrote: > > >>> Apart from the xorg-manpages special casing in mergebase.sh, this > > >>> should even allow portupgrade -a to work correctly. I am not sure > > >>> why xorg-manpages needs to be special-cased; it looks like the > > >>> manpages are migrating into xorg-docs, so can't we use a MOVED entry > > >>> to do that? > > >> > > >> Some of them are migrating to separate lib* ports. > > > > > > OK, but to a first approximation we can use xorg-docs? > > > > Nope, xorg-docs is teh new xorg-documents, with papers and stuff, but > > almost no manpages. Manual pages are installed per-port. > > OK. We'll need to check how portupgrade handles it with a "deleted" > entry in MOVED. I think it will prompt to delete it, but worst case > is it just gets left behind in /usr/X11R6 and should not interfere > with the upgrade anyway. Except that if it is left behind it will remove files belonging to other ports upon removal. Still, these are just manpages so nothing would stop working and when someone notices they are gone they can reinstall new port to which the missing manpages belong to get them back. Dejan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704162159.02888.dejan.lesjak>