Date: Sat, 24 Nov 2012 14:55:47 -0500 (EST) From: Benjamin Kaduk <kaduk@MIT.EDU> To: Glen Barber <gjb@freebsd.org> Cc: freebsd-doc@freebsd.org Subject: Re: Request for Review: pkgng documentation for the Handbook Message-ID: <alpine.GSO.1.10.1211241453410.2164@multics.mit.edu> In-Reply-To: <20121124172712.GB1470@glenbarber.us> References: <20121116165810.GC1335@glenbarber.us> <20121123173758.GA1282@glenbarber.us> <alpine.GSO.1.10.1211232216260.2164@multics.mit.edu> <20121124172712.GB1470@glenbarber.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Nov 2012, Glen Barber wrote: > On Fri, Nov 23, 2012 at 11:52:37PM -0500, Benjamin Kaduk wrote: >> On Fri, 23 Nov 2012, Glen Barber wrote: > >> % <para>The package database conversion may emit errors as the >> % contents are converted to the new version. Generally, these >> % errors can be safely ignored, however a list of third-party >> % software that was not successfully converted will be listed >> % after <command>pkg2ng</command> has finished. These must be >> % fixed by hand.</para> >> >> Is that "fix by hand" going to be deinstall/reinstall most of the time? >> We might want to say so. >> > > Yes, that is on my todo list for the next set of changes. I want to get > this into the Handbook though, so people have some documentation on how > things work. Fixing things "by hand" with pkgng is a bit tricky, and > can have a number of edge cases, so it will be a large-ish addition. Ah, having not had to deal with it myself, I didn't realize the potential for complications. Definitely best to leave it out of this round, then. >> % <para>Unlike the <filename >> % role="package">ports-mgmt/portmaster</filename> and >> % <filename role="package">ports-mgmt/portupgrade</filename> >> % ports, the order in which the new and old versions are >> % listed differ. For <application>pkgng</application>, the >> % syntax is <command>pkg set -o >> >> My broswer puts a line break between the '-' and the 'o', which seems >> very odd. I don't know that there's a markup fix for that, though; I just >> mention it as odd. >> > > I'll switch this to <screen> tags then. The other alternative would be > to use , but that's... ugly. I don't think would help the issue I saw, as the line break was mid-word (the "word" being "-o"). -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1211241453410.2164>