So, spec file:

* BuildRequires:

 - All BR must not be on the same line (max 76), vim is your friend...
 - There're some BR which're not necessary to be set ( such as "make",
"autoconf", "gcc" "and automake").
 - All others are not quite good, you must use -devel package (e.g libXext-devel).
 - xorg-x11-proto-devel is redundant as libX11-devel (which should be set
instead of libX11) is require by libXinerama-devel.
 - libX11-devel is redundant as libXinerama-devel requires libX11-devel.
 - check for some other BR too.

* Requires

 - You should really think about what x2vnc requires to be able to start and
work correctly.
 - According to me, x2vnc doesn't work alone.
 - Check this.

* %prep

 - the use of "cp -f x2vnc.man x2vnc.man.orig" is useless. You don't need to
create an save file.
 - Also the use of "mv -f new_man x2vnc.man" is useless.
 - Just use :
   iconv -f iso-8859-5 -t utf-8 x2vnc.man > x2vnc.man
   instead of
   iconv -f iso-8859-5 -t utf-8 x2vnc.man > new_man

* %build
 - sounds good.

* %install

 - The use of "mkdir -p $RPM_BUILD_ROOT" is useless.
   Buildroot is already created by default.
 - You should add timestamp in your "make install" : INSTALL="install -p".

* %changelog

 - please add a DOT to "Initial packaging" sentence.

Spec URL: http://www.stahnkage.com/rpms/x2vnc.spec
SRPM URL: http://www.stahnkage.com/rpms/x2vnc-1.7.2-2.src.rpm



>* BuildRequires:
>
> - All BR must not be on the same line (max 76), vim is your friend...
Fixed
> - There're some BR which're not necessary to be set ( such as "make",
>"autoconf", "gcc" "and automake").
Removed.  Not sure what I was thinking here :)
> - All others are not quite good, you must use -devel package (e.g libXext-devel).
Reworked this section.  
> - xorg-x11-proto-devel is redundant as libX11-devel (which should be set
>instead of libX11) is require by libXinerama-devel.
> - libX11-devel is redundant as libXinerama-devel requires libX11-devel.
> - check for some other BR too.
I pulled all devel libs that appear to be needed and tried installing each to
see if they pulled each other.  They don't appear to, at least not the final set
listed in BR.
>
>* Requires
>
> - You should really think about what x2vnc requires to be able to start and
>work correctly.
> - According to me, x2vnc doesn't work alone.
> - Check this.
x2vnc requires almost nothing to run.  Look at the spec for xterm, it requires
nothing.  Ideally, I would require an X11 session of some sort, but I am not
sure what syntax to use for "X must be present".
>
>* %prep
>
> - the use of "cp -f x2vnc.man x2vnc.man.orig" is useless. You don't need to
>create an save file.
> - Also the use of "mv -f new_man x2vnc.man" is useless.
> - Just use :
>   iconv -f iso-8859-5 -t utf-8 x2vnc.man > x2vnc.man
>   instead of
>   iconv -f iso-8859-5 -t utf-8 x2vnc.man > new_man
Changed
>
>* %build
> - sounds good.
>
>* %install
>
> - The use of "mkdir -p $RPM_BUILD_ROOT" is useless.
>   Buildroot is already created by default.
> - You should add timestamp in your "make install" : INSTALL="install -p".
Changed
>
>* %changelog
>
> - please add a DOT to "Initial packaging" sentence.
Ok

Just one comment:

(In reply to comment #1)
> 
> * %prep
> 
>  - the use of "cp -f x2vnc.man x2vnc.man.orig" is useless. You don't need to
> create an save file.
>  - Also the use of "mv -f new_man x2vnc.man" is useless.
>  - Just use :
>    iconv -f iso-8859-5 -t utf-8 x2vnc.man > x2vnc.man
>    instead of
>    iconv -f iso-8859-5 -t utf-8 x2vnc.man > new_man

  This is forbidden. Direct redirect use of iconv destroys the
  original file. Actually in -2 binary man file is broken.

and what about the use of
find ./man -name "*.1" -exec iconv -f iso8859-2 -t utf8 {} -o {}utf \;

Well, actually files needed to be fixed are
only ./x2vnc.man (in build directory), aren't they?

So simply in %prep stage:
---------------------------------------------
for f in README x2vnc.man ; do
  iconv -f ISO08859-2 -t UTF-8 $f > $f.tmp && \
    mv $f.tmp $f || rm -f $f.tmp
done
---------------------------------------------
will be simpler (this is my usual way).

And I do Agree with that...

It's goog and clean.

http://www.stahnkage.com/rpms/x2vnc-1.7.2-3.src.rpm
http://www.stahnkage.com/rpms/x2vnc.spec

Changes made. 

full review is coming up ;-)

OK - Package meets naming and packaging guidelines
OK - Spec file matches base package name.
OK - Spec has consistant macro usage.
OK - Meets Packaging Guidelines.
OK - License is GPL
OK - License field in spec matches
OK - License file included in package
OK - Spec in American English
OK - Spec is legible.
OK - Sources match upstream md5sum:
OK - Package has correct buildroot
OK - BuildRequires correct
OK - Requires isn't required
OK - Patch is correctly applied and work.
OK - Package compiles and builds on at least one arch (i386).
OK - Package preserves timestamps on files.
OK - Package has %defattr and permissions on files is good.
OK - Package has a correct %clean section.
OK - Package is code or permissible content.
OK - Packages %doc files present and don't affect runtime.
OK - Package has no duplicate files in %files.
OK - Package doesn't own any directories other packages own.
OK - Package has a correct %changelog section.

OK - Mock build on i386 and x86_64 (FC-6 and FC-devel)
OK - RPMLINT is silent on both RPM and SRPM.


SHOULD Items:

OK - Should build on all supported archs
OK - Should function as described.
OK - Should package latest version

----

APPROVED by me

----

seems okay also to me, except that I don't think the following
lines are needed:
------------------------------------------
pwd
ls
------------------------------------------

Ho...I omited to mentione that.

Michael, remove "pwd" and "ls" commands before request CVSSync.

Mamoru, i wonder whether the %{?dist} tag shouldn't be used to avoid trouble in
cvs import/build procedure ?

New Package CVS Request
=======================
Package Name: x2vnc
Short Description:  Dual screen hack for VNC
Owners: mastahnke
Branches: FC6
InitialCC: 

I also removed the pwd and ls, and will put that new version in CVS .