Seems to be available in FreeBSD base system:

https://www.freebsd.org/cgi/man.cgi?query=soelim&apropos=0&sektion=0&manpath=FreeBSD+10.0-RELEASE&arch=default&format=html

On 09/10/14 13:09, Paul Alfille wrote:
> I'd never heard of soelim -- it looks better than the sed-based
> scripts we are using.
>
> For background, the problem all this is addressing is that there is a
> lot of redundancy in the text of the various man files for the
> different devices and prgrams. In fact that's the point of owfs: to
> have a consistent scheme for addressing and managing 1-wire devices.
>
> Keeping all the common text blocks consistent was increasingly
> difficult, so the .so file for including common blocks was introduced.
> Apparently .so files are a problem for installation so adding a build
> script to perform the inclusion was introduced, but that in turn
> depended on non-portable behavior.
>
> Is soelim available on all platforms?
>
> Paul
>
> On Thu, Oct 9, 2014 at 6:45 AM, Stefano Miccoli <mo...@icloud.com
> <mailto:mo...@icloud.com>> wrote:
>
>     That's my fault... (due to a patch I submitted long ago in order
>     to have man pages under OSX).
>
>     .so files are NOT man pages, but files included via .so groff
>     directives in other man pages.
>
>     In previous versions of owfs, a non portable script processed
>     those includes before installing man pages. Unfortunately the
>     script relied on GNU utilities not available by default on darwin
>     (and afaik also not on BSD): therefore I proposed to install the
>     .so files unchanged along with the man pages. (Simplistic solution
>     but very portable, ...)
>
>     If the .so files clutter too much  the man tree (but actually I
>     would not care about this) I can write a patch to run 'soelim' on
>     the man pages before installation or move the .so files to a
>     location where they cannot be mistaken for man pages. Of course I
>     have to check before where the standard place for .so files is....
>
>     Sorry 
>
>     Stefano
>
>     PS:
>
>     That strange configuration.1so file becomes, when included in
>     owserver:
>
>     *CONFIGURATION* *FILE*
>        *-c* *file* *|* *--configuration* *file*
>            Name  of  an *owfs* *(5)* configuration file with more
>     command line parame-
>            ters
>
>     but cannot be processed alone, since most of the man pages
>     machinery is loaded by the "master" man page.
>
>     On 09 Oct 2014, at 09:08, Johan Ström <jo...@stromnet.se
>     <mailto:jo...@stromnet.se>> wrote:
>
>>     Thanks, now it works better!
>>
>>     FreeBSD port submitted:
>>     https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194261
>>
>>
>>     There seems to be some new man-files installed, which in my
>>     opinion is a bit too commonly-named:
>>     +man/man1/cmdline_mini.1so.gz
>>     +man/man1/configuration.1so.gz
>>     +man/man1/description.1so.gz
>>     +man/man1/device.1so.gz
>>     +man/man1/format.1so.gz
>>     ... and so on.
>>     (Full pkg-plist diff:
>>     
>> https://github.com/stromnet/freebsd-ports/commit/27f00a6e436d224ea9940ed530280163fcaf5cdc#diff-3)
>>
>>     In addition, they are not too informative.. For example:
>>
>>     $ man configuration
>>     Name of an configuration file with more command line parameters
>>     $
>>
>>     /Johan
>>
>>
>>     On 09/10/14 03:27, Paul Alfille wrote:
>>>     Ok, that was embarrassing.
>>>
>>>     I hadn't tested building from a fresh directory the download
>>>     file rather than just packaging up the development directory
>>>     with "make dist"
>>>
>>>     Basically I commented the "lint" stuff from the two Makefiles. 
>>>
>>>     OWFS 2.9p7
>>>     Release Notes
>>>
>>>     Oct 8, 2014
>>>
>>>     Fix build problems, otherwise no changes.
>>>
>>>     -----------------------
>>>
>>>     OWFS 2.9p6
>>>     Release Notes
>>>
>>>     Oct 7, 2014
>>>
>>>     One Wire File System
>>>     www.owfs.org <http://www.owfs.org/>
>>>
>>>     New Features
>>>     1. HobbyBoards Masterhub
>>>     A. New 4-port hub
>>>     B. USB suport
>>>     C. Ethernet not yet implemented
>>>     D. Autodiscovery not yet implemented
>>>     2. New HobbyBoards Sensors
>>>     A. Updated Moisture Meter
>>>     B. Humidity
>>>     C. Barometer
>>>     3. Improved systemd support -- Tomasz Torcz
>>>
>>>     Fixes
>>>     1. Mutex errors and checking, including read-write lock error --
>>>     Christian Magnusson
>>>     2. Longer timeput needed for FTDI serial adapters -- Johan Ström
>>>     3. FreeBSD fixes -- Johan Ström
>>>     4. mucl C library support -- der_tiger and Szabocls Nagy
>>>     5. Numerous fixes found by Coverity analysis
>>>     6. Configuration script fixes from Christian Magnusson and
>>>     der_tiger 
>>>     7. owcapi bug in OW_present -- Valery Grusdev
>>>     8. ownet payload size off by one -- Hans-Frieder Vogt
>>>     9. OSX mutex error -- Stefano Miccoli
>>>     10. Show HobbyBoard device version in decimal rather than hex
>>>     11. MAX31850 Termocouple correction -- Paul Panish
>>>     12. Endiaan fix for DS2408 -- Johan Ström
>>>     13. DS18B20 resolution fix -- Johan Ström
>>>     14. Python trouble with verion from CVS -- Johan Ström
>>>
>>>
>>>
>>>     
>>> ------------------------------------------------------------------------------
>>>     Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>     Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>>     Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>     Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>     
>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>
>>>
>>>     _______________________________________________
>>>     Owfs-developers mailing list
>>>     Owfs-developers@lists.sourceforge.net 
>>> <mailto:Owfs-developers@lists.sourceforge.net>
>>>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>     
>> ------------------------------------------------------------------------------
>>     Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>     Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>>     Reports
>>     Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>     Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>     
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk_______________________________________________
>>     Owfs-developers mailing list
>>     Owfs-developers@lists.sourceforge.net
>>     <mailto:Owfs-developers@lists.sourceforge.net>
>>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>     
> ------------------------------------------------------------------------------
>     Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>     Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>     Reports
>     Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>     Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>     
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>     _______________________________________________
>     Owfs-developers mailing list
>     Owfs-developers@lists.sourceforge.net
>     <mailto:Owfs-developers@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to