Request for Review: pkgng documentation for the Handbook

Benjamin Kaduk kaduk at MIT.EDU
Sat Nov 24 19:55:57 UTC 2012


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


More information about the freebsd-doc mailing list