Hi, I couldn't find your package, only the one in git: http://git.debian.org/?p=users/derevko-guest/fspy.git;a=summary I have also made a package for fspy for ubuntu: http://revu.ubuntuwire.com/details.py?package=fspy https://code.edge.launchpad.net/~medigeek/+junk/fspy http://bazaar.launchpad.net/~medigeek/+junk/fspy/files I don't think it's necessary to patch the Makefile, I've managed to compile mine without patching it (on Ubuntu at least). Also, by comparing, I've noticed that my manpage looks a bit better (attached). Lastly, the source should contain a file "COPYING" for proper licensing: http://code.google.com/p/fspy/issues/detail?id=1
Attachment:
fspy.8
Description: Binary data
<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!-- Process this file with docbook-to-man to generate an nroff manual
page: `docbook-to-man manpage.sgml > manpage.8'. You may view
the manual page with: `docbook-to-man manpage.sgml | nroff -man |
less'. A typical entry in a Makefile or Makefile.am is:
manpage.8: manpage.sgml
docbook-to-man $< > $@
The docbook-to-man binary is found in the docbook-to-man package.
Please remember that if you create the nroff version in one of the
debian/rules file targets (such as build), you will need to include
docbook-to-man in your Build-Depends control field.
-->
<!-- Fill in your name for FIRSTNAME and SURNAME. -->
<!ENTITY dhfirstname "<firstname>Savvas</firstname>">
<!ENTITY dhsurname "<surname>Radevic</surname>">
<!-- Please adjust the date whenever revising the manpage. -->
<!ENTITY dhdate "<date>January 30, 2009</date>">
<!-- SECTION should be 1-8, maybe w/ subsection other parameters are
allowed: see man(7), man(1). -->
<!ENTITY dhsection "<manvolnum>8</manvolnum>">
<!ENTITY dhemail "<email>vicedar@gmail.com</email>">
<!ENTITY dhusername "Savvas Radevic">
<!ENTITY dhucpackage "<refentrytitle>FSPY</refentrytitle>">
<!ENTITY dhpackage "fspy">
<!ENTITY debian "<productname>Debian</productname>">
<!ENTITY gnu "<acronym>GNU</acronym>">
<!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
]>
<refentry>
<refentryinfo>
<address>
&dhemail;
</address>
<author>
&dhfirstname;
&dhsurname;
</author>
<copyright>
<year>2009</year>
<holder>&dhusername;</holder>
</copyright>
&dhdate;
</refentryinfo>
<refmeta>
&dhucpackage;
&dhsection;
</refmeta>
<refnamediv>
<refname>&dhpackage;</refname>
<refpurpose>Filesystem activity monitoring tool</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>&dhpackage;</command>
<arg><option>options</option></arg>
<arg><option>file/dir</option></arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>DESCRIPTION</title>
<para>This manual page documents briefly the
<command>&dhpackage;</command>
command (using "&dhpackage; --help").</para>
<para>This manual page was written for the &debian; distribution
because the original program does not have a manual page.
Instead, it has documentation in the &gnu;
<application>Info</application> format; see below.</para>
<para><command>&dhpackage;</command> is an easy to use Linux filesystem activity
monitoring tool which is meant to be small, fast and
to handle system resources conservative. You can apply
filters, use diffing and your own output format in
order to get the best results.</para>
</refsect1>
<refsect1>
<title>OPTIONS</title>
<para>These programs follow the usual &gnu; command line syntax,
with long options starting with two dashes (`-'). A summary of
options is included below. For a complete description, see the
<application>Info</application> files.</para>
<variablelist>
<varlistentry>
<term><option>-h</option>
<option>--help</option>
</term>
<listitem>
<para>Show summary of options.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>--version</option>
</term>
<listitem>
<para>Show version of program.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-F</option>
<option>--filter STRING/REGEX</option>
</term>
<listitem>
<para>A string or regular expression which will be used to filter the output.
(the regex will be matched against the whole path e.g. [/etc/passwd])</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-I</option>
<option>--inverted STRING/REGEX</option>
</term>
<listitem>
<para>Its the same like -F/--filter but inverted. you can combine both.
e.g. -F '.conf' -I 'wvdial.conf' will filter for files with ".conf"
in its name but without "wvdial.conf" in it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-I</option>
<option>--recursive NUMBER</option>
</term>
<listitem>
<para>Its the same like -F/--filter but inverted. you can combine both.
e.g. -F '.conf' -I 'wvdial.conf' will filter for files with ".conf"
in its name but without "wvdial.conf" in it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-A</option>
<option>--adaptive</option>
</term>
<listitem>
<para>(HIGHLY-EXPERIMENTAL) Enables the adaptive mode. e.g. if new items will be added
within the path fspy will automatically add those items to the watch list.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-D</option>
<option>--diff VALUE</option>
</term>
<listitem><para>(EXPERIMENTAL) Enables the diffing feature.
VALUE may be a comma separated list of:
s - element size (byte)
A - last access time (e.g. Mon Jul 21 21:32:31 2008)
M - last modification time (e.g. Mon Jul 21 21:32:31 2008)
S - last status change time (e.g. Mon Jul 21 21:32:31 2008)
O - permissions (octal)
U - owner (uid)
G - group (gid)
I - inode number
D - device id
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-T</option>
<option>--type VALUE</option>
</term>
<listitem><para>Specifies the type of objects to look for.
VALUE may be a comma separated list of:
f - regular file
d - directory
s - symlink
p - FIFO/pipe
c - character device
b - block device
o - socket
default is any.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>-O</option>
<option>--output VALUE</option>
</term>
<listitem><para>Specifies output format.
VALUE may be a comma separated list of:
f - filename
p - path
d - access description
t - element type
s - element size (byte)
w - watch descriptor (inotify manpage)
c - cookie (inotify manpage)
m - access mask (inotify manpage | src/fsevents.h)
l - len (inotify manpage)
A - last access time (e.g. Mon Jul 21 21:32:31 2008)
M - last modification time (e.g. Mon Jul 21 21:32:31 2008)
S - last status change time (e.g. Mon Jul 21 21:32:31 2008)
O - permissions (octal)
U - owner (uid)
G - group (gid)
I - inode number
D - device id
T - date and time (for this event) (e.g. Tue Mar 25 09:23:16 CET 2008)
e.g.: `[,T,], ,d,:,p,f' would result in:
`[Mon Sep 1 12:31:25 2008] file was opened:/etc/passwd'
(take a look at the README).
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>This manual page was written by &dhusername; &dhemail; for
the &debian; system (but may be used by others). Permission is
granted to copy, distribute and/or modify this document under
the terms of the &gnu; General Public License, Version 2 any
later version published by the Free Software Foundation.
</para>
<para>
On Debian systems, the complete text of the GNU General Public
License can be found in /usr/share/common-licenses/GPL.
</para>
</refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->