Open GoogleCodeExporter opened 9 years ago
Ok, thanks.
There is also some man page stuff on the list here:
http://groups.google.com/group/opkg-devel/browse_thread/thread/10ff67aa0f55973c/
88bd02302e806567?lnk=gst&q=opkg+help+and+documentation#88bd02302e806567
Its not particularly polished, nor is it all relevant to opkg.
Original comment by graham.g...@gmail.com
on 5 Aug 2010 at 11:31
I've committed your man pages. Thanks David.
Original comment by graham.g...@gmail.com
on 10 Aug 2010 at 5:41
[deleted comment]
Wow !
Nice catch. I searched the development mailing-list, but I did not found any
work regarding this purpose. I've just merged proposed manpages and my former
work. Patch enclosed.
I fixed suggested manpages in order to provide a coherent documentation. I also
added symbolic links at install step (ipk -> opk format file, opkg -> opkg-cl),
I think it'll be easier to call the relevant man page.
Thanks.
Original comment by david.ba...@grassvalley.com
on 10 Aug 2010 at 1:29
Attachments:
The opk.5 and opk-control.5 pages are not accurate nor complete and the
copyright is dubious (looks like the file is pulled from Debian). If corrected,
it would be better off going into a wiki than manual pages. This would make it
more accessible, considering most opkg installations are on embedded systems
which quite likely won't install the man program.
An opkg.conf man page would be relevant. But again, this one has many omissions
and inaccuracies.
Original comment by graham.g...@gmail.com
on 12 Aug 2010 at 1:05
Further documentation is on the roadmap but I won't have time for it for a
while yet...
Manpages for the config files, package file format and package control fields
will all eventually be needed.
Original comment by paul.betafive
on 18 Sep 2013 at 1:21
The manpage for opkg.conf needs to address issue 64.
Original comment by paul.betafive
on 28 Sep 2013 at 1:28
Original issue reported on code.google.com by
david.ba...@grassvalley.com
on 5 Aug 2010 at 9:21Attachments: