Re: [ITA] doxygen

[Ken Brown via Cygwin-apps]

On 10/17/2020 9:43 AM, Achim Gratz wrote:

Ken Brown writes:

There's no need for a new release at the moment, but I'm attaching the cygport
file I would use if there were.  It differs in only very minor ways from the
current cygport file (also attached).


For your problem with the debuginfo that we've briefly discussed on IRC:

It turns out I had exactly the same problem before, for exactly the same
reason (Qt moc-generated interface headers) and the same fix works just
as well for doxygen:

CFLAGS+=" -femit-struct-debug-reduced"

That gets you debuginfo packages for both architectures (I didn't have
graphviz installed when building the package locally, but I doubt it
makes a difference for this issue).  I doubt anyone is going to notice
the difference due to the less detailed debugging information… :-)


Thanks!  That's good to know.

Ken

Re: [ITA] doxygen

[Achim Gratz]

Ken Brown writes:
> There's no need for a new release at the moment, but I'm attaching the 
> cygport 
> file I would use if there were.  It differs in only very minor ways from the 
> current cygport file (also attached).

For your problem with the debuginfo that we've briefly discussed on IRC:

It turns out I had exactly the same problem before, for exactly the same
reason (Qt moc-generated interface headers) and the same fix works just
as well for doxygen:

CFLAGS+=" -femit-struct-debug-reduced"

That gets you debuginfo packages for both architectures (I didn't have
graphviz installed when building the package locally, but I doubt it
makes a difference for this issue).  I doubt anyone is going to notice
the difference due to the less detailed debugging information… :-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

Re: [ITA] doxygen

[Andrew Schulman]

> Am 11.11.2018 um 23:38 schrieb Ken Brown:
> > There's no need for a new release at the moment, but I'm attaching the 
> > cygport
> > file I would use if there were.  It differs in only very minor ways from the
> > current cygport file (also attached).
> >
> > I've tested that the upstream git repo builds and passes all tests.
> >
> > Ken
> >
> 
> updated  cygwin-pkg-maint

Gold star awarded! https://cygwin.com/goldstars/#KB

Re: [ITA] doxygen

[Andrew Schulman]

> Am 11.11.2018 um 23:38 schrieb Ken Brown:
> > There's no need for a new release at the moment, but I'm attaching the 
> > cygport
> > file I would use if there were.  It differs in only very minor ways from the
> > current cygport file (also attached).
> >
> > I've tested that the upstream git repo builds and passes all tests.
> >
> > Ken
> >
> 
> updated  cygwin-pkg-maint

Gold star awarded! https://cygwin.com/goldstars/#KB

Re: [ITA] doxygen

[Marco Atzeri]

Am 11.11.2018 um 23:38 schrieb Ken Brown:

There's no need for a new release at the moment, but I'm attaching the cygport
file I would use if there were.  It differs in only very minor ways from the
current cygport file (also attached).

I've tested that the upstream git repo builds and passes all tests.

Ken



updated  cygwin-pkg-maint

Regards
Marco

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

[ITA] doxygen

[Ken Brown]

There's no need for a new release at the moment, but I'm attaching the cygport 
file I would use if there were.  It differs in only very minor ways from the 
current cygport file (also attached).

I've tested that the upstream git repo builds and passes all tests.

Ken
NAME="doxygen"
VERSION=1.8.15
RELEASE=0.1

HOMEPAGE="http://www.doxygen.org/";

GIT_URI="https://github.com/doxygen/doxygen.git";
inherit qt4-cmake git

# SRC_URI="http://ftp.stack.nl/pub/users/dimitri/${P}.src.tar.gz";
SRC_URI+=" 
http://pkgs.fedoraproject.org/repo/pkgs/doxygen/doxywizard.png/1a84da877450422c5fc49e525c546cd4/doxywizard.png";

SUMMARY="A documentation system for C++ and other languages"
DESCRIPTION="Doxygen is a documentation system for C++, C, Java, Objective-C, 
IDL
(Corba and Microsoft flavours) and to some extent PHP, C#, and D."
CATEGORY="Devel"

DEPEND="libQtCore4-devel libxapian-devel libclang-devel clang 
libllvm-devel-static texlive-collection-fontutils"

PKG_NAMES="doxygen doxygen-doxywizard"

doxygen_SUMMARY="${SUMMARY}"
doxygen_DESCRIPTION="${DESCRIPTION}"
doxygen_CATEGORY="Devel"
doxygen_CONTENTS="usr/share/doc"
for prog_name in doxygen doxyindexer doxysearch.cgi
do
doxygen_CONTENTS+=" usr/bin/${prog_name}.exe"
doxygen_CONTENTS+=" usr/share/man/man1/${prog_name/.cgi/}.1.gz"
done

doxygen_doxywizard_SUMMARY="Doxywizard is a graphical front-end to 
read/edit/write doxygen configuration files and to launch doxygen"
doxygen_doxywizard_DESCRIPTION="Doxywizard is a graphical front-end to 
read/edit/write doxygen configuration files and to launch doxygen."
doxygen_doxywizard_CATEGORY="Devel"
doxygen_doxywizard_REQUIRES="doxygen"
doxygen_doxywizard_CONTENTS='usr/bin/doxywizard.exe 
usr/share/man/man1/doxywizard.1.gz usr/share/applications usr/share/pixmaps'

src_compile() {
# Starting with version 1.8.5, doxygen can store data gathered in a
# sqlite3 database. This is an experimental feature and so is
# disabled here. If you wish to enable this feature then set the
# 'use_sqlite' variable to "ON".
local use_sqlite="OFF"

# Enable clang-assisted parsing.
local use_libclang="ON"

# We can enable 'doxyindexer' and 'doxysearch' since we have
# libxapian-devel as a build dependency.
local build_search="ON"

# Doxygen fails to compile under 64-bit Cygwin if the cygport values
# of CFLAGS and CXXFLAGS are passed through (the assembler generates
# the error 'too many sections'). This means that we don't generate a
# debuginfo package for 64-bit builds. The error is not given if -O0
# is used (i.e. disable compiler optimisation), but an optimised
# build is probably more important than a debuginfo package.
local build_type="RelWithDebInfo"
if [ "${ARCH}" == "x86_64" ]; then
CFLAGS="-pipe -Wall -Werror=format-security 
-Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=4"
CXXFLAGS="${CFLAGS}"
build_type="Release"
fi

# Ensure that strdup(3) and killpg(2) are visible.
CFLAGS+=" -D_DEFAULT_SOURCE"
CXXFLAGS+=" -D_DEFAULT_SOURCE"

cd "${B}"
qt4_cmake_compile \
-Dbuild_wizard=ON \
    -Dbuild_doc=ON\
-Dbuild_xmlparser=ON  \
-Dbuild_search=${build_search}\
-Duse_sqlite3=${use_sqlite}   \
    -Duse_libclang=${use_libclang}\
-DCMAKE_BUILD_TYPE=${build_type}  \
-DCMAKE_VERBOSE_MAKEFILE=ON   \
-DDOC_INSTALL_DIR="/share/doc/doxygen"

make docs
}

src_install() {
cd "${B}"
cyginstall

# Add a desktop menu entry.
newicon "${S}/doxywizard.png" doxywizard.png
make_desktop_entry doxywizard "Doxygen Wizard" doxywizard "Development"
}

src_test() {
cd "${B}"
make tests
}
# doxygen.cygport
inherit qt4-cmake
NAME="doxygen"
VERSION=1.8.14
RELEASE=2
SUMMARY="A documentation system for C++, C, Java, Objective-C, IDL (Corba and 
Microsoft flavours) and to some extent PHP, C#, and D"
DESCRIPTION="Doxygen is a documentation system for C++, C, Java, Objective-C, 
IDL (Corba and Microsoft flavours) and to some extent PHP, C#, and D."
CATEGORY="Devel"

########

doxygen Notes (was: Re: Moving on from Cygwin)

[David Stacey]

On 27/06/18 11:14, Michael Wild wrote:

For me the following orphaned packages are of importance (not all of
them David's):

* doxygen

If nobody else steps up, I can adopt one or the other.


Some notes on 'doxygen' that might help you (or someone else) maintain 
the package:


doxygen is split into two packages: the main programme in 'doxygen', and 
the 'doxywizard' GUI in 'doxygen-doxywizard'. It GUI icon used for 
doxywizard is borrowed from the Fedora package and is part of kdesdk.


New doxygen releases are put out upstream once or twice a year (pay 
attention around Christmas Day!) [1]. Between releases, it's worth 
checking the patches that get applied to doxygen in a major distro, e.g 
[2], and pick up any that you feel are important.


Doxygen has it's own C++ parser, which is quite 'loose' in its 
understanding of C++. It's generally OK, but I've tripped it up in the 
past with some complex template specialisation. Thankfully, doxygen can 
be built to use clang for its parsing (although you have to explicitly 
enable this in your doxygen file [3]). I build doxygen in this way to 
give users the option of a 'better' C++ parser should they need it 
(although I'm not aware of any major distro doing likewise).


Doxygen has an experimental feature to store its internal data in an 
sqlite3 database. This is turned off, and I'm not aware of any major 
distro enabling this feature.


Doxygen fails to compile under 64-bit Cygwin with the default CFLAGS and 
CXXFLAGS as populated by cygport. The compilation fails in the assembler 
with 'too many sections'. The solution is to suppress the generation of 
the 'debuginfo' package for 64-bit, and then the compilation completes 
successfully. This doesn't affect 32-bit Cygwin, where a 'debuginfo' 
package is generated.


Hope that helps,

Dave.

[1] - http://doxygen.org/manual/changelog.html
[2] - https://src.fedoraproject.org/cgit/rpms/doxygen.git/tree/
[3] - http://doxygen.org/manual/config.html#cfg_clang_assisted_parsing

Re: [RFU] doxygen-1.8.5-1

[Yaakov (Cygwin/X)]

On 2013-09-09 01:15, David Stacey wrote:

# 32-bit:
# 64-bit:


Uploaded.


Please delete 1.8.3.1 and leave 1.8.4 as previous.


Done.


Yaakov

[RFU] doxygen-1.8.5-1

[David Stacey]

# 32-bit:
BASEURL=https://dl.dropboxusercontent.com/u/119453582/Cygwin/32bit/release
wget --no-check-certificate --no-host-directories --force-directories 
--cut-dirs=5 \

${BASEURL}/doxygen/doxygen-1.8.5-1-src.tar.bz2 \
${BASEURL}/doxygen/doxygen-1.8.5-1.tar.bz2 \
${BASEURL}/doxygen/doxygen-debuginfo/doxygen-debuginfo-1.8.5-1.tar.bz2 \
${BASEURL}/doxygen/doxygen-debuginfo/setup.hint \
${BASEURL}/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.5-1.tar.bz2 \
${BASEURL}/doxygen/doxygen-doxywizard/setup.hint \
${BASEURL}/doxygen/setup.hint


# 64-bit:
BASEURL=https://dl.dropboxusercontent.com/u/119453582/Cygwin/64bit/release
wget --no-check-certificate --no-host-directories --force-directories 
--cut-dirs=5 \

${BASEURL}/doxygen/doxygen-1.8.5-1-src.tar.bz2 \
${BASEURL}/doxygen/doxygen-1.8.5-1.tar.bz2 \
${BASEURL}/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.5-1.tar.bz2 \
${BASEURL}/doxygen/doxygen-doxywizard/setup.hint \
${BASEURL}/doxygen/setup.hint


Please delete 1.8.3.1 and leave 1.8.4 as previous.
Note that the 64-bit version is missing clang-assisted parsing, and does 
not have a debuginfo package.


Many thanks,

Dave.

Re: [64bit RFU] doxygen-1.8.4-2

[marco atzeri]

Il 6/8/2013 12:28 AM, David Stacey ha scritto:



Please remove 1.8.4-1 and leave 1.8.3.1-2 as previous.


uploaded and removed 1.8.4-1



Many thanks in advance for uploading,

Dave.



Regards
Marco

[64bit RFU] doxygen-1.8.4-2

[David Stacey]

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-check-certificate --no-host-directories --force-directories 
--cut-dirs=5 \

${BASEURL}/3K51NHzNNn/64bit/release/doxygen/doxygen-1.8.4-2.tar.bz2 \
${BASEURL}/gk-C_A3MKE/64bit/release/doxygen/doxygen-1.8.4-2-src.tar.bz2 \
${BASEURL}/07f8FokqQW/64bit/release/doxygen/setup.hint \
${BASEURL}/Y0kci6wcka/64bit/release/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.4-2.tar.bz2 
\

${BASEURL}/mYehMAzZ16/64bit/release/doxygen/doxygen-doxywizard/setup.hint


Please remove 1.8.4-1 and leave 1.8.3.1-2 as previous.

This is a rebuild of doxygen for 64-bit Cygwin with the following 
improvements:


* Doxygen is now able to generate latex using texlive-collection. A PDF 
version of the doxygen manual has been produced in this way and is 
included in the binary package;


* The doxywizard GUI has been built using the Qt4 libraries.

Note that there is no 64-bit version of libclang at the moment, and 
therefore the 'clang assisted parsing' feature has not been compiled in. 
I will rebuild doxygen when libclang is available.


Many thanks in advance for uploading,

Dave.

Re: [64bit RFU] doxygen-1.8.4-1

[Yaakov (Cygwin/X)]

On 2013-05-21 15:32, David Stacey wrote:

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-host-directories --force-directories --cut-dirs=5 \
${BASEURL}/UGu_bsP8XW/64bit/release/doxygen/doxygen-1.8.4-1-src.tar.bz2 \
${BASEURL}/ZRfN9VKFzW/64bit/release/doxygen/doxygen-1.8.4-1.tar.bz2 \
${BASEURL}/07f8FokqQW/64bit/release/doxygen/setup.hint


Uploaded.


Yaakov

[64bit RFU] doxygen-1.8.4-1

[David Stacey]

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-host-directories --force-directories --cut-dirs=5 \
${BASEURL}/UGu_bsP8XW/64bit/release/doxygen/doxygen-1.8.4-1-src.tar.bz2 \
${BASEURL}/ZRfN9VKFzW/64bit/release/doxygen/doxygen-1.8.4-1.tar.bz2 \
${BASEURL}/07f8FokqQW/64bit/release/doxygen/setup.hint


This is a minimal build of doxygen-1.8.4 for 64-bit Cygwin:

* There is no TeX support in Cygwin64 at the moment, so you will need to 
specify 'GENERATE_LATEX = NO' in your doxygen configuration file. For 
the same reason, there is no PDF version of the manual in this build.


* There is no libclang in Cygwin64 at the moment, so this build does not 
have the 'clang assisted parsing' feature that is present in the 32-bit 
version.


* There is no Qt4 support in Cygwin64 at the moment, so this build is 
provided without the doxywizard sub-package.


* Compiling with --ggdb produces a compilation error (too many sections) 
which I am unable to work around. Hence there is no debuginfo package 
for this build.


I will rebuild doxygen when 64-bit versions of clang / Qt4 / 
texlive-collection become available.


Cheers,

Dave.

Re: [RFU] doxygen-1.8.4

[Yaakov (Cygwin/X)]

On 2013-05-20 12:08, David Stacey wrote:

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7

[snip]

Please delete 1.8.2-1 and leave 1.8.3.1-1 as previous.


Done and done.


Yaakov

[RFU] doxygen-1.8.4

[David Stacey]

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-check-certificate --no-host-directories --force-directories 
--cut-dirs=4 \

${BASEURL}/D5wIQxCe9e/release/doxygen/doxygen-1.8.4-1-src.tar.bz2 \
${BASEURL}/7ldGx1Ng8M/release/doxygen/doxygen-1.8.4-1.tar.bz2 \
${BASEURL}/S0WLMr_y8z/release/doxygen/setup.hint \
${BASEURL}/7UyhsHmI7f/release/doxygen/doxygen-debuginfo/doxygen-debuginfo-1.8.4-1.tar.bz2 
\

${BASEURL}/o9JY-YlExo/release/doxygen/doxygen-debuginfo/setup.hint \
${BASEURL}/VIVP0Hk5ih/release/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.4-1.tar.bz2 
\

${BASEURL}/e6GGPYhIEC/release/doxygen/doxygen-doxywizard/setup.hint


Please delete 1.8.2-1 and leave 1.8.3.1-1 as previous.
64-bit version to follow in a couple of days.

Many thanks,

Dave.

Re: 64bit doxygen-1.8.3.1-1: compilation error [ATTN: Yaakov]

[Yaakov (Cygwin/X)]

On 2013-04-01 09:39, David Stacey wrote:

Thank you for building a 64-bit version of doxygen. As doxygen
maintainer, I wanted to rebuild this myself (mainly so that it was built
for linux-g++ rather than win32-g++). However, when I try to re-build
your doxygen-1.8.3.1-1 package with cygport, I get the following error:

sh: epstopdf: command not found
error: Problems running epstopdf. Check your TeX installation!

There is no TeX in the 64-bit distribution yet, so please could you
describe how you managed to build this package.


http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/doxygen

IIRC I cross-compiled this from i686.


Yaakov

Re: [64bit RFU] doxygen-1.8.3.1-2

[marco atzeri]

On 4/4/2013 9:46 PM, David Stacey wrote:

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-host-directories --force-directories --cut-dirs=5 \
${BASEURL}/GaHtPI0wwe/64bit/release/doxygen/doxygen-1.8.3.1-2-src.tar.bz2 \
${BASEURL}/dnd_KE3crB/64bit/release/doxygen/doxygen-1.8.3.1-2.tar.bz2 \
${BASEURL}/07f8FokqQW/64bit/release/doxygen/setup.hint



This is a very minimalistic build of doxygen 1.8.3.1, compiled for
64-bit. Please note the following:

* There is no TeX support in Cygwin64 at the moment, so you will need to
specify 'GENERATE_LATEX = NO' in your doxygen configuration file. For
the same reason, there is no PDF version of the manual in this build.

* There is no Qt4 support in Cygwin64 at the moment, so this build is
provided without the doxywizard sub-package.

* Compiling with --ggdb produces a compilation error (too many sections)
which I will investigate if I get time. The upshot of this is that there
is no debuginfo package for this build.

* This build replaces doxygen-1.8.3.1-1, which was built for win32-g++
and would not compile under Cygwin64 as it relied on a TeX installation.

I will re-build doxygen when 64-bit versions of Qt4 / texlive-collection
become available.

Cheers,

Dave.



uploaded

Marco

[64bit RFU] doxygen-1.8.3.1-2

[David Stacey]

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-host-directories --force-directories --cut-dirs=5 \
${BASEURL}/GaHtPI0wwe/64bit/release/doxygen/doxygen-1.8.3.1-2-src.tar.bz2 \
${BASEURL}/dnd_KE3crB/64bit/release/doxygen/doxygen-1.8.3.1-2.tar.bz2 \
${BASEURL}/07f8FokqQW/64bit/release/doxygen/setup.hint



This is a very minimalistic build of doxygen 1.8.3.1, compiled for 
64-bit. Please note the following:


* There is no TeX support in Cygwin64 at the moment, so you will need to 
specify 'GENERATE_LATEX = NO' in your doxygen configuration file. For 
the same reason, there is no PDF version of the manual in this build.


* There is no Qt4 support in Cygwin64 at the moment, so this build is 
provided without the doxywizard sub-package.


* Compiling with --ggdb produces a compilation error (too many sections) 
which I will investigate if I get time. The upshot of this is that there 
is no debuginfo package for this build.


* This build replaces doxygen-1.8.3.1-1, which was built for win32-g++ 
and would not compile under Cygwin64 as it relied on a TeX installation.


I will re-build doxygen when 64-bit versions of Qt4 / texlive-collection 
become available.


Cheers,

Dave.

64bit doxygen-1.8.3.1-1: compilation error [ATTN: Yaakov]

[David Stacey]

Yaakov,

Thank you for building a 64-bit version of doxygen. As doxygen 
maintainer, I wanted to rebuild this myself (mainly so that it was built 
for linux-g++ rather than win32-g++). However, when I try to re-build 
your doxygen-1.8.3.1-1 package with cygport, I get the following error:


sh: epstopdf: command not found
error: Problems running epstopdf. Check your TeX installation!

There is no TeX in the 64-bit distribution yet, so please could you 
describe how you managed to build this package.


Many thanks in advance for your help,

Dave.

Re: [RFU] doxygen-1.8.3.1-1

[Corinna Vinschen]

On Jan 22 19:40, David Stacey wrote:
> BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
> wget --no-host-directories --force-directories --cut-dirs=4 \
> ${BASEURL}/c0cvFMR4a5/release/doxygen/doxygen-1.8.3.1-1-src.tar.bz2 \
> ${BASEURL}/p4a4gFk1Cp/release/doxygen/doxygen-1.8.3.1-1.tar.bz2 \
> ${BASEURL}/S0WLMr_y8z/release/doxygen/setup.hint \
> ${BASEURL}/ugpJO9smb6/release/doxygen/doxygen-debuginfo/doxygen-debuginfo-1.8.3.1-1.tar.bz2
> \
> ${BASEURL}/o9JY-YlExo/release/doxygen/doxygen-debuginfo/setup.hint \
> ${BASEURL}/pLgkFFyLXR/release/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.3.1-1.tar.bz2
> \
> ${BASEURL}/e6GGPYhIEC/release/doxygen/doxygen-doxywizard/setup.hint
> 
> 
> Please delete 1.8.0-1, leaving 1.8.2-1 as previous.

Done.


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

[RFU] doxygen-1.8.3.1-1

[David Stacey]

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-host-directories --force-directories --cut-dirs=4 \
${BASEURL}/c0cvFMR4a5/release/doxygen/doxygen-1.8.3.1-1-src.tar.bz2 \
${BASEURL}/p4a4gFk1Cp/release/doxygen/doxygen-1.8.3.1-1.tar.bz2 \
${BASEURL}/S0WLMr_y8z/release/doxygen/setup.hint \
${BASEURL}/ugpJO9smb6/release/doxygen/doxygen-debuginfo/doxygen-debuginfo-1.8.3.1-1.tar.bz2 
\

${BASEURL}/o9JY-YlExo/release/doxygen/doxygen-debuginfo/setup.hint \
${BASEURL}/pLgkFFyLXR/release/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.3.1-1.tar.bz2 
\

${BASEURL}/e6GGPYhIEC/release/doxygen/doxygen-doxywizard/setup.hint


Please delete 1.8.0-1, leaving 1.8.2-1 as previous.

Many thanks,

Dave.

Re: [RFU] doxygen-1.8.2-1

[Corinna Vinschen]

On Dec  8 19:39, David Stacey wrote:
> BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
> wget --no-host-directories --force-directories --cut-dirs=4 \
> ${BASEURL}/ryH8hDaamt/release/doxygen/doxygen-1.8.2-1-src.tar.bz2 \
> ${BASEURL}/ZeHjPqNE49/release/doxygen/doxygen-1.8.2-1.tar.bz2 \
> ${BASEURL}/S0WLMr_y8z/release/doxygen/setup.hint \
> ${BASEURL}/t0lelNR5eC/release/doxygen/doxygen-debuginfo/doxygen-debuginfo-1.8.2-1.tar.bz2
> \
> ${BASEURL}/o9JY-YlExo/release/doxygen/doxygen-debuginfo/setup.hint \
> ${BASEURL}/_Ns3GRitOP/release/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.2-1.tar.bz2
> \
> ${BASEURL}/e6GGPYhIEC/release/doxygen/doxygen-doxywizard/setup.hint
> 
> 
> This introduces new sub-packages doxygen-doxywizard and doxygen-debuginfo.
> 
> Please delete 1.7.4-1, leaving 1.8.0-1 as previous.

Done.


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

[RFU] doxygen-1.8.2-1

[David Stacey]

BASEURL=http://dl.dropbox.com/sh/7y1yn4whbyho9a7
wget --no-host-directories --force-directories --cut-dirs=4 \
${BASEURL}/ryH8hDaamt/release/doxygen/doxygen-1.8.2-1-src.tar.bz2 \
${BASEURL}/ZeHjPqNE49/release/doxygen/doxygen-1.8.2-1.tar.bz2 \
${BASEURL}/S0WLMr_y8z/release/doxygen/setup.hint \
${BASEURL}/t0lelNR5eC/release/doxygen/doxygen-debuginfo/doxygen-debuginfo-1.8.2-1.tar.bz2 
\

${BASEURL}/o9JY-YlExo/release/doxygen/doxygen-debuginfo/setup.hint \
${BASEURL}/_Ns3GRitOP/release/doxygen/doxygen-doxywizard/doxygen-doxywizard-1.8.2-1.tar.bz2 
\

${BASEURL}/e6GGPYhIEC/release/doxygen/doxygen-doxywizard/setup.hint


This introduces new sub-packages doxygen-doxywizard and doxygen-debuginfo.

Please delete 1.7.4-1, leaving 1.8.0-1 as previous.

Many thanks,

Dave.

Re: [ITP] doxygen-1.8.0-1

[Corinna Vinschen]

On Oct  4 22:31, David Stacey wrote:
> 
> wget \
>   http://www.drstacey.talktalk.net/doxygen-1.8.0-1.tar.bz2 \
>   http://www.drstacey.talktalk.net/doxygen-1.8.0-1-src.tar.bz2 \
>   http://www.drstacey.talktalk.net/setup.hint \
>   http://www.drstacey.talktalk.net/md5.sum

Uploaded.  Please send an announcement to the cygwin-announce ML
as described on http://cygwin.com/setup.html#submitting


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

[ITP] doxygen-1.8.0-1

[David Stacey]

wget \
  http://www.drstacey.talktalk.net/doxygen-1.8.0-1.tar.bz2 \
  http://www.drstacey.talktalk.net/doxygen-1.8.0-1-src.tar.bz2 \
  http://www.drstacey.talktalk.net/setup.hint \
  http://www.drstacey.talktalk.net/md5.sum


Revised package that implements suggestions made by Warren Young and 
Christopher Faylor:


  - latex directory has been removed, replaced with a PDF of the 
doxygen manual;

  - README has reference to TeTeX corrected;
  - build number has gone back to '-1'.

Thanks once again to all those who have taken time to help with my first 
contribution.


Dave.

Re: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[David Stacey]

On 03/10/12 21:37, Warren Young wrote:

On 10/2/2012 1:10 PM, David Stacey wrote:

On 02/10/12 02:27, Warren Young wrote:

You should keep using -1 for subsequent build attempts

>

Apologies for that. I was following the advice here:
http://cygwin.com/setup.html#submitting


I was sure I'd seen Corinna complain about a -1 to -2 during a similar 
discussion over a proposed package upload, but even if my recollection 
is correct, I think the public document takes precedence.




Thanks to Warren and Christopher for the clarification. I'll revert to a 
-1 name - you all have to promise not to get confused :-)



2. /usr/share/doc/doxygen/latex should be removed,


I agree completely, but I kept the 'latex' directory for a couple of
reasons. Firstly, this was consistent with the previous build of doxygen
(1.7.4-1), which included the latex directory [1].


Yes, I realize you were just following my previous example, but I'm 
far from infallible.  I saw something in your package I would have 
removed from mine if I'd realized that at the time.


I had a private e-mail yesterday from someone requesting that the latex 
directory be retained. No reason was given. If Sergio would like to 
reply to the mailing list with his reasons then I will consider them. 
However, in the absence of a compelling argument, Warren has convinced 
me: the latex directory will go. I'll generate a PDF of the manual and 
include that as Warren suggested.



There's a bogus test in Doxygen's configure script, where it goes
looking for dot(1) from GraphViz.  It does a weak check for it in a
few common locations, and yells if it isn't there.  dot(1) being a
filter, there isn't a huge penalty for using the native Windows
version, which of course doesn't get installed in any of those
locations.  It would be nice to either 1) send upstream a test using
the PATH instead of a hardcoded list; or 2) adopt Yaakov's GraphViz
package:


If the configure script doesn't detect dot(1) then it isn't the end of
the world - you can specify the location of the dot executable by
specifying DOT_PATH in the project configuration file:


Are you sure Doxygen doesn't use dot during the package build process, 
such as part of building Doxygen's own manual?  I don't see why it 
would bother trying to find it at configure time otherwise.


There is a HAVE_DOT in the project configuration file, and I was hoping 
that doxygen might be clever and default this to YES or NO based on the 
test in the configure file - but I don't think it does! I've had a quick 
grep through the source code, and the only apparent use of this dot(1) 
check is that one of the examples gets skipped if dot(1) is missing.


I will try to have the next doxygen package ready for about this time 
tomorrow. Thank you for all your advice with this - hopefully we're 
nearly there now!


Dave.

RE: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[Buchbinder, Barry (NIH/NIAID) [E]]

David Stacey sent the following at Tuesday, October 02, 2012 3:11 PM
>http://cygwin.com/setup.html#submitting

"Package acceptation"
 ^^^

Might "acceptance" be a better word?
http://en.wiktionary.org/wiki/acceptation

(I originally thought that "acceptation" isn't an English word, but it
is.)

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

Re: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[Christopher Faylor]

On Wed, Oct 03, 2012 at 02:37:34PM -0600, Warren Young wrote:
>On 10/2/2012 1:10 PM, David Stacey wrote:
>> On 02/10/12 02:27, Warren Young wrote:
>>> You should keep using -1 for subsequent build attempts
> >
>> Apologies for that. I was following the advice here:
>> http://cygwin.com/setup.html#submitting
>
>I was sure I'd seen Corinna complain about a -1 to -2 during a similar 
>discussion over a proposed package upload, but even if my recollection 
>is correct, I think the public document takes precedence.

I think I recall Corinna making that point and I agree with it.  We should
change the public document.  I'd rather just refine the -1 version than
announce a new -47 version once all of the kinks have been worked out.

cgf

Re: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[Warren Young]

On 10/2/2012 1:10 PM, David Stacey wrote:

On 02/10/12 02:27, Warren Young wrote:

You should keep using -1 for subsequent build attempts

>

Apologies for that. I was following the advice here:
http://cygwin.com/setup.html#submitting


I was sure I'd seen Corinna complain about a -1 to -2 during a similar 
discussion over a proposed package upload, but even if my recollection 
is correct, I think the public document takes precedence.



2. /usr/share/doc/doxygen/latex should be removed,


I agree completely, but I kept the 'latex' directory for a couple of
reasons. Firstly, this was consistent with the previous build of doxygen
(1.7.4-1), which included the latex directory [1].


Yes, I realize you were just following my previous example, but I'm far 
from infallible.  I saw something in your package I would have removed 
from mine if I'd realized that at the time.



Secondly, I rather
thought that if 'make install' wanted to install the latex directory
then it wasn't really my place to delete of it.


That's a much stronger argument.

You might ask on the Doxygen mailing list why they think Joe User wants 
the LaTeX manual sources installed.  It might be something they've 
overlooked in their build system.



However, I've had a little look at a couple of popular Linux
distributions, and neither Fedora [2] nor Ubuntu [3] include the latex
directory in their doxygen packages.


Ditto RHEL.


There's a bogus test in Doxygen's configure script, where it goes
looking for dot(1) from GraphViz.  It does a weak check for it in a
few common locations, and yells if it isn't there.  dot(1) being a
filter, there isn't a huge penalty for using the native Windows
version, which of course doesn't get installed in any of those
locations.  It would be nice to either 1) send upstream a test using
the PATH instead of a hardcoded list; or 2) adopt Yaakov's GraphViz
package:


If the configure script doesn't detect dot(1) then it isn't the end of
the world - you can specify the location of the dot executable by
specifying DOT_PATH in the project configuration file:


Are you sure Doxygen doesn't use dot during the package build process, 
such as part of building Doxygen's own manual?  I don't see why it would 
bother trying to find it at configure time otherwise.

Re: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[David Stacey]

On 02/10/12 02:27, Warren Young wrote:
You should keep using -1 for subsequent build attempts until one gets 
RFU'd.  Use new package versions only to disambiguate published 
package versions.  The package version number is there to help 
setup.exe out, not to help us poor humans out. :)


Apologies for that. I was following the advice here: 
http://cygwin.com/setup.html#submitting


"Do increase the version number no matter what... even if has only been 
discussed in mailing list and never uploaded: it costs nothing and 
avoids confusion in both setup.exe and people mind."


Maybe someone would be kind enough to clarify when the version number 
should be bumped up and when it shouldn't.



Nits:

1. Another build requirement change: the doxygen.README file still 
refers to TeTeX, which was replaced recently with TeX Live.  But, 
installing a basic TeX setup alone isn't enough.  To build the PDF 
manual, you need the optional texlive-collection-fontutils package for 
epstopdf, and texlive-collection-latexextra for float.sty. There's no 
need to mention any other packages.  Installing those two into a stock 
Cygwin install will drag in enough of the remaining TeX stuff to build 
the manual.


Good spot. I'll correct the reference to TeTeX and submit another 
version. For my own sanity I'll call it 1.8.0-3, unless someone 
clarifies the version-bumping quote first.


2. /usr/share/doc/doxygen/latex should be removed, in favor of a 
.../pdf subdirectory.  I don't see a reason to ship source and 
intermediate build files here, expecting the user to build the docs.  
What's wanted here is a PDF of the LaTeX *output*.


I agree completely, but I kept the 'latex' directory for a couple of 
reasons. Firstly, this was consistent with the previous build of doxygen 
(1.7.4-1), which included the latex directory [1]. Secondly, I rather 
thought that if 'make install' wanted to install the latex directory 
then it wasn't really my place to delete of it.


However, I've had a little look at a couple of popular Linux 
distributions, and neither Fedora [2] nor Ubuntu [3] include the latex 
directory in their doxygen packages. Fedora includes the HTML manual and 
some examples in the main 'doxygen' package; Ubuntu has the HTML manual, 
the examples and the PDF manual in a separate 'doxygen-doc' package [4].


The upshot of this little investigation is that I'm happy to generate 
the PDF and remove the latex intermediary files. But I see this as an 
enhancement (rather than a mistake that needs correcting), so I'll do 
this in the next release of doxygen that I package.


[1] http://cygwin.com/packages/doxygen/doxygen-1.7.4-1
[2] 
https://admin.fedoraproject.org/pkgdb/builds/show/F-17-i386/doxygen/1/1.8.0/1.fc17/i686#files

[3] http://packages.ubuntu.com/quantal/i386/doxygen/filelist
[4] http://packages.ubuntu.com/quantal/all/doxygen-doc/filelist

3. I'd rather see your first version be 1.8.2-1 instead.  Why start 
with a version two bug fix releases back?


The reason for this is simply down to the amount of testing that I've 
given the packages. I've given 1.8.0 a rather thorough testing in a 
Cygwin environment. I'm happy that it works reliably, has no major bugs 
and improves upon the 1.7.4 build we have at the moment.


Sometimes these "bug fix releases" introduce more bugs than they fix, 
which is why I'm not going for 1.8.1!


I have a build of 1.8.2 for Cygwin, but I have done *much* less testing 
of it. This version also builds the doxywizard GUI as a separate 
package, but this has had next to no testing. I'd sooner release 
something that I have confidence in. When I've got that same level of 
confidence in 1.8.2 (maybe in a couple of months) then I'll upload that 
version.


There's a bogus test in Doxygen's configure script, where it goes 
looking for dot(1) from GraphViz.  It does a weak check for it in a 
few common locations, and yells if it isn't there.  dot(1) being a 
filter, there isn't a huge penalty for using the native Windows 
version, which of course doesn't get installed in any of those 
locations.  It would be nice to either 1) send upstream a test using 
the PATH instead of a hardcoded list; or 2) adopt Yaakov's GraphViz 
package:


If the configure script doesn't detect dot(1) then it isn't the end of 
the world - you can specify the location of the dot executable by 
specifying DOT_PATH in the project configuration file:


http://www.stack.nl/~dimitri/doxygen/config.html#cfg_dot_path

But even that shouldn't be necessary: Cygwin adds the Windows path to 
its own PATH, so provided that the Windows 'dot.exe' is in your Windows 
path and you've set HAVE_DOT=YES in your project configuration file, you 
/should/ get GraphViz graphs in your doxygen output.


When I'm more p

Re: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[Warren Young]

On 9/29/2012 1:21 PM, David Stacey wrote:


wget \
   http://www.drstacey.talktalk.net/doxygen-1.8.0-2.tar.bz2 \
   http://www.drstacey.talktalk.net/doxygen-1.8.0-2-src.tar.bz2 \
   http://www.drstacey.talktalk.net/setup.hint \
   http://www.drstacey.talktalk.net/md5.sum


You should keep using -1 for subsequent build attempts until one gets 
RFU'd.  Use new package versions only to disambiguate published package 
versions.  The package version number is there to help setup.exe out, 
not to help us poor humans out. :)


Nits:

1. Another build requirement change: the doxygen.README file still 
refers to TeTeX, which was replaced recently with TeX Live.  But, 
installing a basic TeX setup alone isn't enough.  To build the PDF 
manual, you need the optional texlive-collection-fontutils package for 
epstopdf, and texlive-collection-latexextra for float.sty.  There's no 
need to mention any other packages.  Installing those two into a stock 
Cygwin install will drag in enough of the remaining TeX stuff to build 
the manual.


2. /usr/share/doc/doxygen/latex should be removed, in favor of a .../pdf 
subdirectory.  I don't see a reason to ship source and intermediate 
build files here, expecting the user to build the docs.  What's wanted 
here is a PDF of the LaTeX *output*.


3. I'd rather see your first version be 1.8.2-1 instead.  Why start with 
a version two bug fix releases back?


Nits aside, I can't withhold a GTG recommendation, since your packages 
are no worse off than mine were, and those were apparently still useful 
to people. :)


Something to pursue later, having no effect on GTG status:

There's a bogus test in Doxygen's configure script, where it goes 
looking for dot(1) from GraphViz.  It does a weak check for it in a few 
common locations, and yells if it isn't there.  dot(1) being a filter, 
there isn't a huge penalty for using the native Windows version, which 
of course doesn't get installed in any of those locations.  It would be 
nice to either 1) send upstream a test using the PATH instead of a 
hardcoded list; or 2) adopt Yaakov's GraphViz package:


http://cygwin.com/ml/cygwin/2010-10/msg00232.html

Option 1 is sufficient, but option 2 means you can make graphviz a 
dependency of your doxygen package, so everyone gets it automatically.

Re: [ITA] doxygen

[Andrew Schulman]

> 
> Hi.
> 
> I contacted the doxygen maintainer, Warren Young, privately because I 
> had encountered a bug [1] in doxygen 1.7.4. I knew that this bug was 
> fixed in later versions of doxygen, and I asked if he could upload a 
> more recent version. Warren replied and very kindly offered me the 
> maintenance of doxygen for Cygwin.
> 
> So I would like to adopt doxygen.

Auto gold star awarded:  http://cygwin.com/goldstars/#DSt

[ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[David Stacey]

wget \
  http://www.drstacey.talktalk.net/doxygen-1.8.0-2.tar.bz2 \
  http://www.drstacey.talktalk.net/doxygen-1.8.0-2-src.tar.bz2 \
  http://www.drstacey.talktalk.net/setup.hint \
  http://www.drstacey.talktalk.net/md5.sum


Many thanks to Marco and Achim for their suggestions. This is a second 
attempt, with the 'setup.hint' file generated by cygport. As the 
dependencies are now being determined automatically, libstdc++6 is now 
included in the 'requires' section.


Dave.


[setup.hint]
category: Devel
requires: libiconv2 libstdc++6
sdesc: "A documentation system for C++, C, Java, Objective-C, IDL (Corba 
and Microsoft flavors) and to some extent PHP, C#, and D."
ldesc: "Doxygen is a documentation system for C++, C, Java, Objective-C, 
IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D."

Re: [ITP] doxygen-1.8.0-1 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[Achim Gratz]

David Stacey writes:
> The package is built with cygport: the 'src' file contains the
> original doxygen source code (unaltered), a couple of patch files and
> the cygport file itself. As I said, this is my first package - please
> be patient with a newbie, and apologies in advance for any mistakes.

You might want to drop the setup.hint from the cygwin.patch file and let
cygport auto-generate it to take care of dependencies.  You'd need to
add (resp. alter) the SUMMARY, DESCRIPTION and CATEGORY variables to the
cygport file to do this.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [ITP] doxygen-1.8.0-1 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[marco atzeri]

On 9/29/2012 2:38 PM, David Stacey wrote:


I appreciate that [ITP] messages are normally reserved for new packages,
but Warren Young suggested that I send this through as an ITP as this is
my first package, and you might want to check it more thoroughly than
for a simple update.

wget \
http://www.drstacey.talktalk.net/doxygen-1.8.0-1.tar.bz2 \
http://www.drstacey.talktalk.net/doxygen-1.8.0-1-src.tar.bz2 \
http://www.drstacey.talktalk.net/setup.hint \
http://www.drstacey.talktalk.net/md5.sum


build and packages are fine. GTG



The package is built with cygport: the 'src' file contains the original
doxygen source code (unaltered), a couple of patch files and the cygport
file itself. As I said, this is my first package - please be patient
with a newbie, and apologies in advance for any mistakes.

Dave.


[setup.hint]
sdesc: "A documentation system for C++, C, Java, Objective-C, IDL (Corba
and Microsoft flavors) and to some extent PHP, C#, and D."
ldesc: "Doxygen is a documentation system for C++, C, Java, Objective-C,
IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D."
category: Devel
requires: libiconv2


$ cygport doxygen-1.8.0-1.cygport deps
  cygwin-1.7.16-1
  libiconv2-1.14-2
  libstdc++6-4.5.3-3

Should  libstdc++6 reported as additional dependency ?

Regards
Marco

[ITP] doxygen-1.8.0-1 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

[David Stacey]

I appreciate that [ITP] messages are normally reserved for new packages, 
but Warren Young suggested that I send this through as an ITP as this is 
my first package, and you might want to check it more thoroughly than 
for a simple update.


wget \
http://www.drstacey.talktalk.net/doxygen-1.8.0-1.tar.bz2 \
http://www.drstacey.talktalk.net/doxygen-1.8.0-1-src.tar.bz2 \
http://www.drstacey.talktalk.net/setup.hint \
http://www.drstacey.talktalk.net/md5.sum

The package is built with cygport: the 'src' file contains the original 
doxygen source code (unaltered), a couple of patch files and the cygport 
file itself. As I said, this is my first package - please be patient 
with a newbie, and apologies in advance for any mistakes.


Dave.


[setup.hint]
sdesc: "A documentation system for C++, C, Java, Objective-C, IDL (Corba 
and Microsoft flavors) and to some extent PHP, C#, and D."
ldesc: "Doxygen is a documentation system for C++, C, Java, Objective-C, 
IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D."

category: Devel
requires: libiconv2

Re: [ITA] doxygen

[marco atzeri]

On 9/29/2012 10:33 AM, David Stacey wrote:


Hi.

I contacted the doxygen maintainer, Warren Young, privately because I
had encountered a bug [1] in doxygen 1.7.4. I knew that this bug was
fixed in later versions of doxygen, and I asked if he could upload a
more recent version. Warren replied and very kindly offered me the
maintenance of doxygen for Cygwin.

So I would like to adopt doxygen.

About me: I am a professional software engineer. I have about 10 years
of Linux experience, and used Solaris for about 6 years prior to that.
Cygwin has been making my life easier for many years now, so a big thank
you to all the maintainers who have worked so hard over the years.

Dave.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=658646



Hi David,
surely no objections, have you already a new package ready to test ?

Regards
Marco

[ITA] doxygen

[David Stacey]

Hi.

I contacted the doxygen maintainer, Warren Young, privately because I 
had encountered a bug [1] in doxygen 1.7.4. I knew that this bug was 
fixed in later versions of doxygen, and I asked if he could upload a 
more recent version. Warren replied and very kindly offered me the 
maintenance of doxygen for Cygwin.


So I would like to adopt doxygen.

About me: I am a professional software engineer. I have about 10 years 
of Linux experience, and used Solaris for about 6 years prior to that. 
Cygwin has been making my life easier for many years now, so a big thank 
you to all the maintainers who have worked so hard over the years.


Dave.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=658646

Re: RFU: doxygen 1.7.4-1

[Corinna Vinschen]

On Aug 10 03:06, Warren Young wrote:
> Updated upstream package.
> 
> wget -e robots=off --cut-dirs=2 -np -nH -A'*1.7.4-1*' -r \
> http://etr-usa.com/cygwin/doxygen/
> 
> Leave current as prev.

Done.


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

RFU: doxygen 1.7.4-1

[Warren Young]

Updated upstream package.

wget -e robots=off --cut-dirs=2 -np -nH -A'*1.7.4-1*' -r \
http://etr-usa.com/cygwin/doxygen/

Leave current as prev.

Re: RFU: doxygen 1.6.1-2

[Warren Young]

On 12/18/2009 3:23 AM, Corinna Vinschen wrote:


There are also older releases left,
1.5.1-1 and 1.5.5-1.  The 1.5.1-1 release is from 2006.  Shall we
remove it?


I'm not emotionally attached to those releases, but then, I don't use 
doxygen on Cygwin.  (I only use one of the packages I maintain.  The 
others are just guests in my shelter for abandoned packages.)


I guess remove them and if someone who actually uses it yells, we can 
put it back.


I don't see a reason to keep 1.5.5 other than general "nice to have a 
prev" reasons.  It's a Cygwin 1.5 package, so if you wanted to clean as 
many of these out of the repo as possible before you release Cygwin 
1.7.1, go for it.

Re: RFU: doxygen 1.6.1-2

[Corinna Vinschen]

On Dec 17 16:12, Warren Young wrote:
> This fixes some packaging errors in -1 and adds manpages to the package.
> 
> wget -e robots=off --cut-dirs=2 -np -nH -A'*1.6.1-2*' -r \
> http://etr-usa.com/cygwin/doxygen/
> 
> Previous -1 should be removed.

Uploaded and 1.6.1-1 removed.  There are also older releases left,
1.5.1-1 and 1.5.5-1.  The 1.5.1-1 release is from 2006.  Shall we
remove it?


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

RFU: doxygen 1.6.1-2

[Warren Young]

This fixes some packaging errors in -1 and adds manpages to the package.

wget -e robots=off --cut-dirs=2 -np -nH -A'*1.6.1-2*' -r \
http://etr-usa.com/cygwin/doxygen/

Previous -1 should be removed.

Re: RFU: doxygen 1.6.1-1

[Corinna Vinschen]

On Dec 11 12:26, Warren Young wrote:
> New upstream release:
> 
> wget -e robots=off --cut-dirs=2 -np -nH -A'*1.6.1-1*' -r \
> http://etr-usa.com/cygwin/doxygen/
> 
> setup.hint unchanged.
> 
> This is the first version packaged explicitly for 1.7.  Previous
> 1.5.5 was copied over from 1.5 repo.

Uploaded.


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

RFU: doxygen 1.6.1-1

[Warren Young]

New upstream release:

wget -e robots=off --cut-dirs=2 -np -nH -A'*1.6.1-1*' -r \
http://etr-usa.com/cygwin/doxygen/

setup.hint unchanged.

This is the first version packaged explicitly for 1.7.  Previous 1.5.5 
was copied over from 1.5 repo.

Re: [RFU] doxygen-1.5.5-1

[Corinna Vinschen]

On May  8 22:38, Warren Young wrote:
> http://etr-usa.com/cygwin/doxygen/setup.hint
> http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2
> http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1-src.tar.bz2

Uploaded.  Thanks for taking over!   <-- Igor?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

[GTG] Re: [RFU] doxygen-1.5.5-1

[Dr. Volker Zell]

> Warren Young writes:

> Dr. Volker Zell wrote:
>> I would also recommend to build outside of the source tree.

> I didn't know it was possible with non-autoconf build systems.  Thank
> you for cluing me in about:

>> lndirs

> this.  :)

>> -MAN1DIR = man/man1
>> +MAN1DIR = share/man/man1

> Yes, too bad there isn't a --mandir switch in Doxygen's configure script.

>> There is also some nice
>> documentation included in the doc directory in the source tree. Maybe
>> you should include it too.

> Done, and re-uploaded to same URLs as previous.

> This step means the package now requires tetex to build.  I hope
> that's okay...

Builds fine from source, packaging and setup.hint look good.

GTG
  Volker
  

Re: [RFU] doxygen-1.5.5-1

[Warren Young]

Dr. Volker Zell wrote:

I would also recommend to build outside of the source tree.


I didn't know it was possible with non-autoconf build systems.  Thank 
you for cluing me in about:



lndirs


this.  :)


-MAN1DIR = man/man1
+MAN1DIR = share/man/man1


Yes, too bad there isn't a --mandir switch in Doxygen's configure script.


There is also some nice
documentation included in the doc directory in the source tree. Maybe
you should include it too.


Done, and re-uploaded to same URLs as previous.

This step means the package now requires tetex to build.  I hope that's 
okay...

Re: [RFU] doxygen-1.5.5-1

[Dr. Volker Zell]

>>>>> Warren Young writes:

> New maintainer, new upstream version, new packaging system.  The
> problems that came up in the ITA thread of last week have been fixed.

> files:
> http://etr-usa.com/cygwin/doxygen/setup.hint
> http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2
> http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1-src.tar.bz2


Your man pages install to /usr/man instead of /usr/share/man. I would
also recommend to build outside of the source tree.

Try the following .cygport and .patch files. There is also some nice
documentation included in the doc directory in the source tree. Maybe
you should include it too.

-- cut here ----
DESCRIPTION="Doxygen source code documentation formatter"
HOMEPAGE="http://www.doxygen.org/";
SRC_URI="http://ftp.stack.nl/pub/users/dimitri/${P}.src.tar.gz";

DIFF_EXCLUDES="config.cpp Makefile Makefile.[dl]* *.pro"

src_compile() {
lndirs
cd ${B}
./configure --prefix /usr --docdir /usr/share/doc/${P} --platform 
linux-g++
cygmake
}

src_install() {
cd ${B}
make install INSTALL=../inst/usr
}
-- cut here 

-- cut here 
diff -urN -x CYGWIN-PATCHES -x 'aclocal.m4*' -x autom4te.cache -x config.cache 
-x config.log -x config.status -x config.h -x config.h.in -x ABOUT-NLS -x 
Makefile.in.in -x Makevars.template -x '*SlackBuild*' -x '*.egg-info' -x 
'*.class' -x '*.pyc' -x '*.mo' -x '*.gmo' -x at-3.1.8-31.install.orig -x 
doxygen-1.5.5-1.cygport.orig -x hdf5-1.6.7-1.src.patch.orig -x 
libmad-0.15.1b-1.sh.orig -x libmcrypt-2.5.8-1.src.patch.orig -x 
postgresql-8.1.4-1.cygport.orig -x rcs-5.7-4.src.patch.orig -x 
template-package.sh.orig -x '*.rej' -x '*.spec' -x '*.temp' -x '*~' -x 
'*.stackdump' -x COPYING -x INSTALL -x compile -x config-ml.in -x config.guess 
-x config.sub -x depcomp -x elisp-comp -x install-sh -x libtool.m4 -x 
ltoptions.m4 -x ltsugar.m4 -x ltversion.m4 -x 'lt~obsolete.m4' -x ltmain.sh -x 
mdate-sh -x missing -x mkinstalldirs -x py-compile -x symlink-tree -x 
texinfo.tex -x ylwrap -x config.rpath -x omf.make -x xmldocs.make -x 
gnome-doc-utils.make -x gnome-doc-utils.m4 -x intltool.m4 -x intltool-extract 
-x intltool-extract.in -x intltool-merge -x intltool-merge.in -x 
intltool-update -x intltool-update.in -x config.cpp -x Makefile -x 
'Makefile.[dl]*' -x '*.pro' origsrc/doxygen-1.5.5/Makefile.in 
src/doxygen-1.5.5/Makefile.in
--- origsrc/doxygen-1.5.5/Makefile.in   2008-01-17 20:18:14.0 +0100
+++ src/doxygen-1.5.5/Makefile.in   2008-05-09 09:23:12.75000 +0200
@@ -50,7 +50,7 @@
 
 DATE=$(shell date "+%B %Y")
 
-MAN1DIR = man/man1
+MAN1DIR = share/man/man1
 
 install: doxywizard_install 
$(INSTTOOL) -d $(INSTALL)/bin
diff -urN -x CYGWIN-PATCHES -x 'aclocal.m4*' -x autom4te.cache -x config.cache 
-x config.log -x config.status -x config.h -x config.h.in -x ABOUT-NLS -x 
Makefile.in.in -x Makevars.template -x '*SlackBuild*' -x '*.egg-info' -x 
'*.class' -x '*.pyc' -x '*.mo' -x '*.gmo' -x at-3.1.8-31.install.orig -x 
doxygen-1.5.5-1.cygport.orig -x hdf5-1.6.7-1.src.patch.orig -x 
libmad-0.15.1b-1.sh.orig -x libmcrypt-2.5.8-1.src.patch.orig -x 
postgresql-8.1.4-1.cygport.orig -x rcs-5.7-4.src.patch.orig -x 
template-package.sh.orig -x '*.rej' -x '*.spec' -x '*.temp' -x '*~' -x 
'*.stackdump' -x COPYING -x INSTALL -x compile -x config-ml.in -x config.guess 
-x config.sub -x depcomp -x elisp-comp -x install-sh -x libtool.m4 -x 
ltoptions.m4 -x ltsugar.m4 -x ltversion.m4 -x 'lt~obsolete.m4' -x ltmain.sh -x 
mdate-sh -x missing -x mkinstalldirs -x py-compile -x symlink-tree -x 
texinfo.tex -x ylwrap -x config.rpath -x omf.make -x xmldocs.make -x 
gnome-doc-utils.make -x gnome-doc-utils.m4 -x intltool.m4 -x intltool-extract 
-x intltool-extract.in -x intltool-merge -x intltool-merge.in -x 
intltool-update -x intltool-update.in -x config.cpp -x Makefile -x 
'Makefile.[dl]*' -x '*.pro' 
origsrc/doxygen-1.5.5/tmake/lib/linux-g++/tmake.conf 
src/doxygen-1.5.5/tmake/lib/linux-g++/tmake.conf
--- origsrc/doxygen-1.5.5/tmake/lib/linux-g++/tmake.conf2006-07-21 
21:54:13.0 +0200
+++ src/doxygen-1.5.5/tmake/lib/linux-g++/tmake.conf2008-05-09 
09:23:12.75000 +0200
@@ -42,7 +42,7 @@
 TMAKE_LFLAGS_SHLIB = -shared
 TMAKE_LFLAGS_SONAME= -Wl,-soname,
 
-TMAKE_LIBS =
+TMAKE_LIBS = -liconv
 TMAKE_LIBS_X11 = -lXext -lX11 -lm
 TMAKE_LIBS_X11SM   = -lICE -lSM
 TMAKE_LIBS_QT  = -lqt
-- cut here 

Ciao
  Volker

[RFU] doxygen-1.5.5-1

[Warren Young]

New maintainer, new upstream version, new packaging system.  The 
problems that came up in the ITA thread of last week have been fixed.


files:
http://etr-usa.com/cygwin/doxygen/setup.hint
http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2
http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1-src.tar.bz2

Re: [ITA] doxygen-1.5.5-1

[Yaakov (Cygwin Ports)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Max Bowsher wrote:
| There is a copy of the libpng source code embedded in the doxygen source
| package. By default it builds a private copy of libpng and embeds it in
| the doxygen binaries. This seemed to me like needless duplication, so I
| made it link against the normal (separately packaged) libpng instead.

Using an embedded libpng is also asking for a security vulnerability.


Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkgbuxUACgkQpiWmPGlmQSOJ4wCcDqFAwitjHp/Vk6Nn6Z06kjCC
AdYAn0xNvPAd/WL1QmHmVkS1h0ac8/30
=auTt
-END PGP SIGNATURE-

Re: [ITA] doxygen-1.5.5-1

[Max Bowsher]

Dave Korn wrote:
> Max Bowsher wrote on 02 May 2008 02:45:
> 
>> Warren Young wrote:
>>> Dave Korn wrote:
>>>> requires: cygwin libpng12
>>>>
>>>>   The requires: line looks wrong to meWhy libpng?
>>> Ask Max. :)
>> Last time I looked there was a copy of libpng embedded in the doxygen
>> source tree. Building another copy seemed rather dumb when it's in the
>> distro as a shared library already, so I made it use the distro version.
>>
>> Quite what it actually uses it for, I'm not sure.
>>
>> Max.
> 
>   ??? Confused now ???  http://cygwin.com/setup.html isn't explicit about
> this, but are we /supposed/ to add dependencies for the source packages to the
> requires line?  And if libpng, why not make, gcc, autoconf, automake, bash
>   etc?

Yes, you are confused now :-)

There is a copy of the libpng source code embedded in the doxygen source
package. By default it builds a private copy of libpng and embeds it in
the doxygen binaries. This seemed to me like needless duplication, so I
made it link against the normal (separately packaged) libpng instead.

Suitably clarified?

Max.



signature.asc
Description: OpenPGP digital signature

RE: [ITA] doxygen-1.5.5-1

[Dave Korn]

Warren Young wrote on 02 May 2008 00:10:

> I can't get graphviz to build cleanly under cygport yet. 

  Looks like you may not need to need to!  Volker's sense of timing is
impeccable :)

cheers,
  DaveK
-- 
Can't think of a witty .sigline today

RE: [ITA] doxygen-1.5.5-1

[Dave Korn]

Max Bowsher wrote on 02 May 2008 02:45:

> Warren Young wrote:
>> Dave Korn wrote:
>>> requires: cygwin libpng12
>>> 
>>>   The requires: line looks wrong to meWhy libpng?
>> 
>> Ask Max. :)
> 
> Last time I looked there was a copy of libpng embedded in the doxygen
> source tree. Building another copy seemed rather dumb when it's in the
> distro as a shared library already, so I made it use the distro version.
> 
> Quite what it actually uses it for, I'm not sure.
> 
> Max.

  ??? Confused now ???  http://cygwin.com/setup.html isn't explicit about
this, but are we /supposed/ to add dependencies for the source packages to the
requires line?  And if libpng, why not make, gcc, autoconf, automake, bash
  etc?


cheers,
  DaveK
-- 
Can't think of a witty .sigline today

Re: [ITA] doxygen-1.5.5-1

[Max Bowsher]

Warren Young wrote:
> Dave Korn wrote:
>> requires: cygwin libpng12
>>
>>   The requires: line looks wrong to meWhy libpng?
> 
> Ask Max. :)

Last time I looked there was a copy of libpng embedded in the doxygen
source tree. Building another copy seemed rather dumb when it's in the
distro as a shared library already, so I made it use the distro version.

Quite what it actually uses it for, I'm not sure.

Max.




signature.asc
Description: OpenPGP digital signature

Re: [ITA] doxygen-1.5.5-1

[Warren Young]

Dave Korn wrote:

requires: cygwin libpng12

  The requires: line looks wrong to meWhy libpng?


Ask Max. :)  It may have had to do with a historical ability to use 
graphviz/dot or something like that.  Max's latest doesn't do this, nor 
does mine, because I can't get graphviz to build cleanly under cygport yet.


libiconv2 added.


http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2


  Packaging looks good.


http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1-src.tar.bz2


  Builds OK.  GTG, apart from clearing up the setup.hint confusion.


Thanks!

RE: [ITA] doxygen-1.5.5-1

[Dave Korn]

Warren Young wrote on 01 May 2008 23:15:

> Taking over maintainership of this package from Max Bowsher.  Ported
> build from g-b-s to cygport and updated from 1.5.1 to 1.5.5, so I'd like
> at least one GTG before I post the RFU message.
> 
> http://etr-usa.com/cygwin/doxygen/setup.hint


sdesc: "A documentation system for C++, C, Java, Objective-C, IDL (Corba and
Microsoft flavors) and to some extent PHP, C#, and D."
ldesc: "Doxygen is a documentation system for C++, C, Java, Objective-C, IDL
(Corba and Microsoft flavors) and to some extent PHP, C#, and D."
category: Devel
requires: cygwin libpng12

  The requires: line looks wrong to me.  According to cygcheck, doxygen.exe
depends on libiconv2 and cygwin, doxytag.exe only on cygwin.  Why libpng?

> http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2

  Packaging looks good.

> http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1-src.tar.bz2

  Builds OK.  GTG, apart from clearing up the setup.hint confusion.

cheers,
  DaveK
-- 
Can't think of a witty .sigline today

[ITA] doxygen-1.5.5-1

[Warren Young]

Taking over maintainership of this package from Max Bowsher.  Ported 
build from g-b-s to cygport and updated from 1.5.1 to 1.5.5, so I'd like 
at least one GTG before I post the RFU message.


http://etr-usa.com/cygwin/doxygen/setup.hint
http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1.tar.bz2
http://etr-usa.com/cygwin/doxygen/doxygen-1.5.5-1-src.tar.bz2

Re: ITP: Doxygen

[Max Bowsher]

Vlad wrote:

Greetings,

   It seems that package has been proposed couple of years ago.  And
was rejected due to licence problems.
Here is the link :
http://sources.redhat.com/ml/cygwin-apps/2003-09/msg00348.html

However several things happend since then.  First the AT&T labs at
cambrige is no more,   and the graphviz  package is now developed by
the  graphviz.org.   Consequently the licence has changed from  some
weird  proprietary AT&T code agreement,  to standard CPL licence which
is an OSD approved licence.

http://www.opensource.org/licenses/cpl1.0.php
http://www.graphviz.org/License.php

...

I'm confused by your subject line.
Did you mean "ITP: Graphviz" ?
If so, it would be best for you to repost, with the correct subject.

Max.

ITP: Doxygen

[Vlad]

Greetings,

   It seems that package has been proposed couple of years ago.  And 
was rejected due to licence problems.

Here is the link :
http://sources.redhat.com/ml/cygwin-apps/2003-09/msg00348.html

However several things happend since then.  First the AT&T labs at 
cambrige is no more,   and the graphviz  package is now developed by 
the  graphviz.org.   Consequently the licence has changed from  some 
weird  proprietary AT&T code agreement,  to standard CPL licence which 
is an OSD approved licence.


http://www.opensource.org/licenses/cpl1.0.php
http://www.graphviz.org/License.php

  Official word from the developers is that the package doesn't come 
compile right out of the box, but various  people have reported success 
in doing so after some tweaking.So if this package is approved I 
will attempt  to track down all the missing dependencies and  create a 
patch for this package to be build under cygwin.


   My primary goal is to buiild the dot program which is used by the 
doxygen package to generate the source  documentation.  I will do my 
best to get the other parts working as well. 

   My general plan  is to use as much shared libraries  ( libgd  , 
libfreetype ) as practical,  and  link the missing libraries  statically.


   Here is my proposed setup hint.The requires section is obviously 
incomplete. 

   
 Vlad


  cut here 
--

sdesc: "graph visualization software"
ldesc: "Graphviz is open source graph visualization software. It has 
several

main graph layout programs,  web and interactive graphical interfaces,
auxiliary tools, libraries, and language bindings.

The Graphviz layout programs take descriptions of graphs in a simple text
language, and make diagrams in several useful formats such as images and
SVG for web pages, Postscript for inclusion in PDF or other documents;
or display in an interactive graph browser.

Graphviz has many useful features for concrete diagrams, such as options
for colors, fonts, tabular node layouts, line styles, hyperlinks, and
custom shapes.

In practice, graphs are usually generated from an external data sources,
but they can also be created and edited manually, either as raw text files
or within a graphical editor. (Graphviz was not intended to be a Visio
replacement, so it is probably frustrating to try to use it that way.)"

category: Graphics
requires: cygwin
external-source: package
  cut here 
--

Re: doxygen-1.4.2_20050421-1 ready for review.

[Christopher Faylor]

On Wed, May 04, 2005 at 08:38:15PM +0100, Max Bowsher wrote:
>doxygen-1.4.2_20050421-1 ready for packaging review:
>
>Setup URL:
>http://unicorn.robinson.cam.ac.uk/~mob22/cygdoxygen/
>
>setup.hint:
>category: Devel
>requires: cygwin libpng12
>sdesc: "A documentation system for C++, C, Java, Objective-C, IDL (Corba 
>and Microsoft flavors) and to some extent PHP, C#, and D."
>ldesc: "Doxygen is a documentation system for C++, C, Java, Objective-C, 
>IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D."

As heretical as it sounds, I don't think there's any reason to review
this.  You've had enough painful experience with packaging for me to
trust that you've gotten this right or, at least, that you'll fix it if
someone complains.

So, I'd say, upload away.

cgf

doxygen-1.4.2_20050421-1 ready for review.

[Max Bowsher]

doxygen-1.4.2_20050421-1 ready for packaging review:
Setup URL:
http://unicorn.robinson.cam.ac.uk/~mob22/cygdoxygen/
setup.hint:
category: Devel
requires: cygwin libpng12
sdesc: "A documentation system for C++, C, Java, Objective-C, IDL (Corba and 
Microsoft flavors) and to some extent PHP, C#, and D."
ldesc: "Doxygen is a documentation system for C++, C, Java, Objective-C, IDL 
(Corba and Microsoft flavors) and to some extent PHP, C#, and D."

Max.

Re: doxygen update please? (I even have a patch!)

[Christopher Faylor]

On Wed, May 04, 2005 at 11:08:30AM -0400, William. Rivet wrote:
>Short version:
>
>I would like to see cygwin's doxygen updated. I think I followed the
>steps to make the needed files for a cygwin distribution but would like
>help. Ideally I would think the maintainer would look at what I have and
>work from there. (even if only to tell me to go fix x-y-z)
>
>Comments? Suggestions?

This isn't a mailing list for update requests.  Please confine yourself to
the main cygwin mailing list.

doxygen update please? (I even have a patch!)

[William. Rivet]

Short version:

I would like to see cygwin's doxygen updated. I think I followed the
steps to make the needed files for a cygwin distribution but would like
help. Ideally I would think the maintainer would look at what I have and
work from there. (even if only to tell me to go fix x-y-z)

Comments? Suggestions?



Longer version

doxygen1.2.18 seems to be the latest cygwin build available for "doxygen".

I had a need for it so I of course didn't start by following the rules
 and emailed the maintainer, Ryunosuke Satoh(RS)...well, I'm
sorry if that email made it through because our email filters had a
field day for 2 days afterwards, something about attachment policies and
potential viruses blah-blah-blah...maybe unrelated, I don't know.

Anyway, I don't really know what I'm doing. I read RS's README and
manually applied the provided patch to the new sources. I didn't
understand all of it, and only had one additional modification to make
before I had a successful build. Then I just followed his README
instructions to make the files that seem to be required.


Feel free to email me directly if you can help me move this along.


Thanks everyone for all your hard work,

Bill

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Corinna Vinschen]

On May  3 12:26, Gary R. Van Sickle wrote:
> FWIW, I fully support your stance that your unilaterally-imposed
> "disqualification" was unwarranted.  At the same time, it's not difficult to
> understand Hans' consternation and reaction to the situation.  Doxygen is a
> very useful package, and it would be sad for the "Cygwin immune system" to
> reject its inclusion on the basis that somebody did too much work.

As usual you're off the point.  Anyway, please move over to cygwin-talk.


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Christopher Faylor]

On Tue, May 03, 2005 at 12:26:20PM -0500, Gary R. Van Sickle wrote:
>FWIW, I fully support your stance that your unilaterally-imposed
>"disqualification" was unwarranted.  At the same time, it's not
>difficult to understand Hans' consternation and reaction to the
>situation.  Doxygen is a very useful package, and it would be sad for
>the "Cygwin immune system" to reject its inclusion on the basis that
>somebody did too much work.

I think this subject is closed:
http://sources.redhat.com/ml/cygwin-apps/2005-05/msg00011.html

It's now time to move on to the actual work of getting the new version
of doxygen into the cygwin release.

cgf

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Christopher Faylor]

On Tue, May 03, 2005 at 11:53:44AM -0500, Gary R. Van Sickle wrote:
>> -Original Message-
>> From: cygwin-apps-owner GROUPIE cygwin KOOK com 
>> [mailto:cygwin-apps-owner GROUPIE cygwin KOOK com] On Behalf Of Corinna 
>> Vinschen
>> Sent: Tuesday, May 03, 2005 9:52 AM
>> To: cygwin-apps GROUPIE cygwin KOOK com
>> Subject: Re: Counter-ITP of doxygen (was: Re: Please upload: 
>> doxygen-1.4.2_20050410-1 (n'th take))
>> 
>> On May  3 13:02, Max Bowsher wrote:
>> > Christopher Faylor wrote:
>> > The fact that a few words of mild intention can be 
>> misinterpreted and 
>> > seed an accidental high tension mess has been amply well 
>> demonstrated 
>> > on the cygwin list recently, in the CGF/GRVS thread.
>> 
>> So you're comparing your specific situation with Gary's years 
>> long history of adding useless comments to cgf's postings in 
>> the Cygwin ML?
>
>Ahem, yeah, let's make that: "...Gary's years long history of taking Chris
>to task for his years-long history of uncalled-for snotty comments."
>
>Surprised Chris himself didn't "keep you honest" there.

http://cygwin.com/acronyms/#PCYMTNQREAIYR

And, again, further discussion in this vein should go to cygwin-talk,
please.

cgf

RE: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Gary R. Van Sickle]

[snip]
> >> So you're comparing your specific situation with Gary's years long 
> >> history of adding useless comments to cgf's postings in the Cygwin 
> >> ML?
> >
> > Ahem, yeah, let's make that: "...Gary's years long history 
> of taking 
> > Chris to task for his years-long history of uncalled-for 
> snotty comments."
> >
> > Surprised Chris himself didn't "keep you honest" there.
> 
> Enough! :-)
> 
> I held that thread up as an example of a misunderstanding 
> creating a mess.
> 
> Let's agree that misunderstandings are unfortunate, and not 
> spread the mess around!
> 
> Max.
> 

I could not agree more, Max.  Misunderstandings are indeed unfortunate.
Misrepresentations are something else entirely.

FWIW, I fully support your stance that your unilaterally-imposed
"disqualification" was unwarranted.  At the same time, it's not difficult to
understand Hans' consternation and reaction to the situation.  Doxygen is a
very useful package, and it would be sad for the "Cygwin immune system" to
reject its inclusion on the basis that somebody did too much work.

-- 
Gary R. Van Sickle
 

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Max Bowsher]

Gary R. Van Sickle wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Corinna Vinschen
Sent: Tuesday, May 03, 2005 9:52 AM
To: cygwin-apps@cygwin.com
Subject: Re: Counter-ITP of doxygen (was: Re: Please upload:
doxygen-1.4.2_20050410-1 (n'th take))
On May  3 13:02, Max Bowsher wrote:
Christopher Faylor wrote:
The fact that a few words of mild intention can be
misinterpreted and
seed an accidental high tension mess has been amply well
demonstrated
on the cygwin list recently, in the CGF/GRVS thread.
So you're comparing your specific situation with Gary's years
long history of adding useless comments to cgf's postings in
the Cygwin ML?
Ahem, yeah, let's make that: "...Gary's years long history of taking Chris
to task for his years-long history of uncalled-for snotty comments."
Surprised Chris himself didn't "keep you honest" there.
Enough! :-)
I held that thread up as an example of a misunderstanding creating a mess.
Let's agree that misunderstandings are unfortunate, and not spread the mess 
around!

Max.

RE: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Gary R. Van Sickle]

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Corinna Vinschen
> Sent: Tuesday, May 03, 2005 9:52 AM
> To: cygwin-apps@cygwin.com
> Subject: Re: Counter-ITP of doxygen (was: Re: Please upload: 
> doxygen-1.4.2_20050410-1 (n'th take))
> 
> On May  3 13:02, Max Bowsher wrote:
> > Christopher Faylor wrote:
> > The fact that a few words of mild intention can be 
> misinterpreted and 
> > seed an accidental high tension mess has been amply well 
> demonstrated 
> > on the cygwin list recently, in the CGF/GRVS thread.
> 
> So you're comparing your specific situation with Gary's years 
> long history of adding useless comments to cgf's postings in 
> the Cygwin ML?

Ahem, yeah, let's make that: "...Gary's years long history of taking Chris
to task for his years-long history of uncalled-for snotty comments."

Surprised Chris himself didn't "keep you honest" there.

-- 
Gary R. Van Sickle

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Max Bowsher]

Corinna Vinschen wrote:
On May  3 13:02, Max Bowsher wrote:
Christopher Faylor wrote:
The fact that a few words of mild intention can be misinterpreted and 
seed
an accidental high tension mess has been amply well demonstrated on the
cygwin list recently, in the CGF/GRVS thread.
So you're comparing your specific situation with Gary's years long history
of adding useless comments to cgf's postings in the Cygwin ML?  I don't
think that's the same and I don't think that's a convincing argument at 
all.=
I was not aware of the history you refer to (I've been skimming subjects and 
reading only selected threads on the cygwin ml for a long time now), and was 
just using it as an isolated example of messages being interpreted in a more 
inflammatory tone than they were intended, reaching quite drastic end 
results.

Max.

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Christopher Faylor]

On Tue, May 03, 2005 at 04:51:46PM +0200, Corinna Vinschen wrote:
>On May  3 13:02, Max Bowsher wrote:
>>Christopher Faylor wrote:
>>The fact that a few words of mild intention can be misinterpreted and
>>seed an accidental high tension mess has been amply well demonstrated
>>on the cygwin list recently, in the CGF/GRVS thread.
>
>So you're comparing your specific situation with Gary's years long
>history of adding useless comments to cgf's postings in the Cygwin ML?
>I don't think that's the same and I don't think that's a convincing
>argument at all.

Big ditto, but any further discussion on this should go to cygwin-talk.
It's certainly not valid here.

Puzzling analogies aside, if maxb wants to be the new doxygen
maintainer, I'll withdraw my objections.

cgf

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Corinna Vinschen]

On May  3 13:02, Max Bowsher wrote:
> Christopher Faylor wrote:
> The fact that a few words of mild intention can be misinterpreted and seed 
> an accidental high tension mess has been amply well demonstrated on the 
> cygwin list recently, in the CGF/GRVS thread.

So you're comparing your specific situation with Gary's years long history
of adding useless comments to cgf's postings in the Cygwin ML?  I don't
think that's the same and I don't think that's a convincing argument at all.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Hans W. Horn]

Max,
no - you have not disqualified yourself in my eyes.
And therefore, you should be the new doxygen owner/maintainer if you want it 
that badly.

I also think that we should put this issue finally to rest, stop pouting and 
get on with life!

greets,
H.
Max Bowsher wrote:
Christopher Faylor wrote:
Otherwise, MaxB has
disqualified himself from doxygen package maintainership,
I would to appeal this, please, because I do not believe it is fair to
censure me for a misunderstanding that I have explained and
apologized for.
The fact that a few words of mild intention can be misinterpreted and
seed an accidental high tension mess has been amply well demonstrated
on the cygwin list recently, in the CGF/GRVS thread.
Max. 

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Max Bowsher]

Christopher Faylor wrote:
Otherwise, MaxB has
disqualified himself from doxygen package maintainership,
I would to appeal this, please, because I do not believe it is fair to 
censure me for a misunderstanding that I have explained and apologized for.

The fact that a few words of mild intention can be misinterpreted and seed 
an accidental high tension mess has been amply well demonstrated on the 
cygwin list recently, in the CGF/GRVS thread.

Max.

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Max Bowsher]

Christopher Faylor wrote:
I've waited several days to respond to this because I wanted to make
sure that I was in the proper emotional state and didn't just fire off a
knee-jerk reaction.
Ditto.
Nevertheless, I remain appalled by this turn of events.  I saw nothing
in Hans' email which indicated that he's unwilling to be cooperative
about packaging problems so I see no reason to pull the package from
him.  Hans is not the first person to have to go through a moderate
amount of pain before getting the packaging right and if the biggest
complaint of his source packaging is that it doesn't contain the cygwin
README, then that is not a big deal.
I don't know how to resolve this situation but I do know for sure that
neither Corinna nor I are going to "reward" someone by making them a
package maintainer after essentially publicly insulting another
volunteer.
I feel a bit annoyed by the above, since I did not intentionally insult 
anyone.

After multiple rounds of email dealing with a single, particularly visible, 
issue - version numbering - which is documented in the Package Contibutor's 
Guide, I took a more in-depth look at the packaging, and discovered that the 
source package did not contain everything necessary to recreate the binary 
package, it did not conform to either of the packaging schemas defined as 
acceptable by the Package Contributor's Guide, nor reasonably documented 
alternative, that it did not strip the binaries (required by the Package 
Contributor's Guide), and that the version number formats were still 
incorrect.

Considering the difficulty involved in getting to that point, and realizing 
that fixing all of the above would amount to an almost complete rewrite of 
the packaging script - or, indeed, replacing it with the g-b-s - I concluded 
that this was not a review process that I could guide to a successful 
conclusion.
There wasn't anyone else who was reviewing the later iterations of the 
packages, so I felt that if I was to simply back away, the package would 
left in an unapproved vacuum.

Having involved myself with doxygen to the extent that I had by then, I felt 
obligated to seek a successful conclusion if in any way I could, and saw 
packaging doxygen myself as s possible route. I recognized that there was a 
certain potential for emotional upset, and after spending a couple of days 
wondering how best to phrase things to mitigate that potential, I opted for 
a simple, brief, matter-of-fact presentation. Evidently, that misfired quite 
spectacularly.

At no point did I intend or imply any disparagement towards Hans.
I'll try to avoid sensitive conversations in the future, since I seem to be 
somewhat inept at translating my intentions into text.

Max.

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Hans W. Horn]

Chris, Corinna & Max,
thanks but no thanks.
I had a real rough start with this, which utterly discouraged me and 
dampened my enthusiasm to maintain
anything at this time considerably!

So please consider doxygen and bash to be up again for grabs!
As far as I am concerned, can't you just let Max be doxygen maintainer if he 
still wants to?
The least I want is to seed trouble among the cygwin core team and long-time 
maintainers such as Max.

H.
Christopher Faylor wrote:
On Sat, Apr 23, 2005 at 12:35:19AM +0100, Max Bowsher wrote:
Hans W. Horn wrote:
Alright,
Max Bowsher wrote:
No, still wrong. You didn't read what I said carefully enough.
You *need* to understand:
Filenames are expected to be EXACTLY:
NAME-VERSION-RELEASE.tar.bz2
NAME-VERSION-RELEASE-src.tar.bz2
I guess I never appreciated the subtle naming convention used for
cygwin packages. Honestly, my impression was that names go all over
the map. Fixed (I think).
+++ doxygen_1.4.2-20050410/doc/language.doc +++
doxygen_1.4.2-20050410/doc/translator_report.txt +++
doxygen_1.4.2-20050410/examples/example.tag
These files are touched during a 'make install_docs'.
Excluded offending diffs from patch.
Having got the superficial naming problems out of the way, I took a
closer look at the source packaging.
There were many issues - the most serious being that the source
package did not even contain the Cygwin specific readme at all - and
many minor deficiencies related to using a home-grown build script,
rather than the tried-and-true cygwin template.
I am sorry, but the conclusion I came to was that it would be less
effort for me to produce my own packages of doxygen, based on the the
generic-build-script, than to assist in getting these packages up to
a good-to-go status.
Accordingly, I hereby ITP doxygen myself:
Setup.exe installation site:
http://unicorn.robinson.cam.ac.uk/~mob22/cygdoxygen/
I've waited several days to respond to this because I wanted to make
sure that I was in the proper emotional state and didn't just fire
off a knee-jerk reaction.
Nevertheless, I remain appalled by this turn of events.  I saw nothing
in Hans' email which indicated that he's unwilling to be cooperative
about packaging problems so I see no reason to pull the package from
him.  Hans is not the first person to have to go through a moderate
amount of pain before getting the packaging right and if the biggest
complaint of his source packaging is that it doesn't contain the
cygwin README, then that is not a big deal.
I don't know how to resolve this situation but I do know for sure that
neither Corinna nor I are going to "reward" someone by making them a
package maintainer after essentially publicly insulting another
volunteer.
Hans, this is still yours if you want it.  Otherwise, MaxB has
disqualified himself from doxygen package maintainership, so I guess
we're in the market for a maintainer again.
cgf

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Corinna Vinschen]

On Apr 25 14:09, Christopher Faylor wrote:
> On Sat, Apr 23, 2005 at 12:35:19AM +0100, Max Bowsher wrote:
> >Accordingly, I hereby ITP doxygen myself:
> 
> I've waited several days to respond to this because I wanted to make
> sure that I was in the proper emotional state and didn't just fire off a
> knee-jerk reaction.
> 
> Nevertheless, I remain appalled by this turn of events.  I saw nothing
> in Hans' email which indicated that he's unwilling to be cooperative
> about packaging problems so I see no reason to pull the package from
> him.  Hans is not the first person to have to go through a moderate
> amount of pain before getting the packaging right and if the biggest
> complaint of his source packaging is that it doesn't contain the cygwin
> README, then that is not a big deal.
> 
> I don't know how to resolve this situation but I do know for sure that
> neither Corinna nor I are going to "reward" someone by making them a
> package maintainer after essentially publicly insulting another
> volunteer.
> 
> Hans, this is still yours if you want it.  Otherwise, MaxB has
> disqualified himself from doxygen package maintainership, so I guess
> we're in the market for a maintainer again.

Hans' binary package looks ok to me.  The source package might have some
minor problems but I'd be dead surprised if not any of my packages would
have problems either.  I don't quite understand all that hype around the
source packages anyway.  The source package provides the sources which
have been used to build the binary package.  That's all, no need to create
a science from it.  A minor problem in the source file is certainly no
reason to kick somebody's a**.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Christopher Faylor]

On Sat, Apr 23, 2005 at 12:35:19AM +0100, Max Bowsher wrote:
>Hans W. Horn wrote:
>>Alright,
>>
>>Max Bowsher wrote:
>>>No, still wrong. You didn't read what I said carefully enough.
>>>You *need* to understand:
>>>Filenames are expected to be EXACTLY:
>>>NAME-VERSION-RELEASE.tar.bz2
>>>NAME-VERSION-RELEASE-src.tar.bz2
>>I guess I never appreciated the subtle naming convention used for cygwin
>>packages. Honestly, my impression was that names go all over the map.
>>Fixed (I think).
>>
>>>>+++ doxygen_1.4.2-20050410/doc/language.doc +++
>>>>doxygen_1.4.2-20050410/doc/translator_report.txt +++
>>>>doxygen_1.4.2-20050410/examples/example.tag
>>>These files are touched during a 'make install_docs'.
>>Excluded offending diffs from patch.
>
>Having got the superficial naming problems out of the way, I took a closer 
>look at the source packaging.
>
>There were many issues - the most serious being that the source package did 
>not even contain the Cygwin specific readme at all - and many minor 
>deficiencies related to using a home-grown build script, rather than the 
>tried-and-true cygwin template.
>
>I am sorry, but the conclusion I came to was that it would be less effort 
>for me to produce my own packages of doxygen, based on the the 
>generic-build-script, than to assist in getting these packages up to a 
>good-to-go status.
>
>Accordingly, I hereby ITP doxygen myself:
>Setup.exe installation site:
>http://unicorn.robinson.cam.ac.uk/~mob22/cygdoxygen/

I've waited several days to respond to this because I wanted to make
sure that I was in the proper emotional state and didn't just fire off a
knee-jerk reaction.

Nevertheless, I remain appalled by this turn of events.  I saw nothing
in Hans' email which indicated that he's unwilling to be cooperative
about packaging problems so I see no reason to pull the package from
him.  Hans is not the first person to have to go through a moderate
amount of pain before getting the packaging right and if the biggest
complaint of his source packaging is that it doesn't contain the cygwin
README, then that is not a big deal.

I don't know how to resolve this situation but I do know for sure that
neither Corinna nor I are going to "reward" someone by making them a
package maintainer after essentially publicly insulting another
volunteer.

Hans, this is still yours if you want it.  Otherwise, MaxB has
disqualified himself from doxygen package maintainership, so I guess
we're in the market for a maintainer again.

cgf

Re: Counter-ITP of doxygen

[Lapo Luchini]

This whole issue seems a pretty stupid reason the get angry, to me... =(

-- 
Lapo Luchini

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Hans W. Horn]

Max Bowsher wrote:
...
Having got the superficial naming problems out of the way, I took a
closer look at the source packaging.
There were many issues - the most serious being that the source
package did not even contain the Cygwin specific readme at all - and
hear - hear (you didn't look, did you?)!
many minor deficiencies related to using a home-grown build script,
rather than the tried-and-true cygwin template.
typical NIH syndrom!
I am sorry, but the conclusion I came to was that it would be less
effort for me to produce my own packages of doxygen, based on the the
generic-build-script, than to assist in getting these packages up to a
good-to-go status.
You're so full of it!
But, honestly, I saw this coming! I'd say - why don't you just shove it!
And seriously, I really can't remember why I even thought it would be a good 
thing to offer my services to maintain anything for the cygwin crowd!
That memory has gotten somewhat hazy!
Bye now!

H.

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Hans W. Horn]

Max Bowsher wrote:
Hans W. Horn wrote:
Max Bowsher wrote:
...
Having got the superficial naming problems out of the way, I took a
closer look at the source packaging.
Superficial? In your earlier complaints you made it sound as if those naming 
issues were of utmost importance!

There were many issues - the most serious being that the source
package did not even contain the Cygwin specific readme at all - and...
hear - hear (you didn't look, did you?)!
Yes, I did.
And just to be sure, I used grep. It was not there.
Interesting! You did a grep on a compressed tarball? Or on a directory tree? 
Quite unconventional.
I would use 'find'. As in:
cd /usr
find ./ -name doxygen*README -print
./share/doc/Cygwin/doxygen-1.4.2_20050410-1.README

many minor deficiencies related to using a home-grown build script,
rather than the tried-and-true cygwin template.
Yup! Guilty as charged!
typical NIH syndrom!
NIH?
"Not Invented Here". Probably doesn't count. Has no cygwin trademark!
I am sorry, but the conclusion I came to was that it would be less
effort for me to produce my own packages of doxygen, based on the
the generic-build-script, than to assist in getting these packages
up to a good-to-go status.
As I see it: the last version of the package I have submitted was as much or 
little conformant to the cygwin guidelines as the package it was meant to 
supercede, or 50% of all the other cygwin packages on the market today.

All Cygwin package maintainers work to the set of guidelines that the
project has designed for itself, and which are posted on the website.
If you desire to help, but lack the time or inclination to meet the
guidelines the project has defined for itself, ...
and which are being modified on the fly, see 
http://cygwin.com/ml/cygwin-apps/2005-04/msg00063.html

...then you will discover that whilst your desire to help is appreciated 
...
Are you sure you mean that?
..., you actual offerings may not actually be helpful to the project.
This is a simple fact. If it angers you... there is nothing I can do
about that.
I'm sure you wouldn't! But that's not what angers me; it is rather arrogance 
and pretence that pushes my button.

In any case : this is not a competition for maintainership - you may keep it 
all for yourself! And I'm out for good!

Re: Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Max Bowsher]

Hans W. Horn wrote:
Max Bowsher wrote:
...
Having got the superficial naming problems out of the way, I took a
closer look at the source packaging.
There were many issues - the most serious being that the source
package did not even contain the Cygwin specific readme at all - and
hear - hear (you didn't look, did you?)!
Yes, I did.
And just to be sure, I used grep. It was not there.
many minor deficiencies related to using a home-grown build script,
rather than the tried-and-true cygwin template.
typical NIH syndrom!
NIH?
I am sorry, but the conclusion I came to was that it would be less
effort for me to produce my own packages of doxygen, based on the the
generic-build-script, than to assist in getting these packages up to a
good-to-go status.
You're so full of it!
But, honestly, I saw this coming! I'd say - why don't you just shove it!
And seriously, I really can't remember why I even thought it would be a 
good
thing to offer my services to maintain anything for the cygwin crowd!
That memory has gotten somewhat hazy!
Bye now!
All Cygwin package maintainers work to the set of guidelines that the 
project has designed for itself, and which are posted on the website. If you 
desire to help, but lack the time or inclination to meet the guidelines the 
project has defined for itself, then you will discover that whilst your 
desire to help is appreciated, you actual offerings may not actually be 
helpful to the project.

This is a simple fact. If it angers you... there is nothing I can do about 
that.

Max.

Counter-ITP of doxygen (was: Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take))

[Max Bowsher]

Hans W. Horn wrote:
Alright,
Max Bowsher wrote:
No, still wrong. You didn't read what I said carefully enough.
You *need* to understand:
Filenames are expected to be EXACTLY:
NAME-VERSION-RELEASE.tar.bz2
NAME-VERSION-RELEASE-src.tar.bz2
I guess I never appreciated the subtle naming convention used for cygwin
packages. Honestly, my impression was that names go all over the map.
Fixed (I think).
+++ doxygen_1.4.2-20050410/doc/language.doc +++
doxygen_1.4.2-20050410/doc/translator_report.txt +++
doxygen_1.4.2-20050410/examples/example.tag
These files are touched during a 'make install_docs'.
Excluded offending diffs from patch.
Having got the superficial naming problems out of the way, I took a closer 
look at the source packaging.

There were many issues - the most serious being that the source package did 
not even contain the Cygwin specific readme at all - and many minor 
deficiencies related to using a home-grown build script, rather than the 
tried-and-true cygwin template.

I am sorry, but the conclusion I came to was that it would be less effort 
for me to produce my own packages of doxygen, based on the the 
generic-build-script, than to assist in getting these packages up to a 
good-to-go status.

Accordingly, I hereby ITP doxygen myself:
Setup.exe installation site:
http://unicorn.robinson.cam.ac.uk/~mob22/cygdoxygen/
Max.

Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take)

[Christopher Faylor]

On Tue, Apr 19, 2005 at 10:42:04AM -0700, Hans W. Horn wrote:
>It's only subtle, until you've digested that in this notation RELEASE is a 
>cygwin version attribute and VERSION is an upstream version attribute 
>(which on its own may already use a similar naming convention, such as 
>doxygen-1.4.2-20050410).
>Confused the hell out of me!

http://cygwin.com/setup.html#naming seems pretty clear to me.

Anyway, doxygen-1.4.2-20050410 is not using a similar naming convention.
It is a version number with a dash in it.  The - is not a "release"
and it should be pretty clear that it can't be a cygwin release given
the above URL.

cgf

Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take)

[Hans W. Horn]

It's only subtle, until you've digested that in this notation RELEASE is a 
cygwin version attribute and VERSION is an upstream version attribute (which 
on its own may already use a similar naming convention, such as 
doxygen-1.4.2-20050410).
Confused the hell out of me!

H.
Christopher Faylor wrote:
On Tue, Apr 19, 2005 at 10:30:12AM -0700, Hans W. Horn wrote:
Max Bowsher wrote:
No, still wrong.  You didn't read what I said carefully enough.  You
*need* to understand:
Filenames are expected to be EXACTLY:
NAME-VERSION-RELEASE.tar.bz2
NAME-VERSION-RELEASE-src.tar.bz2
I guess I never appreciated the subtle naming convention used for
cygwin packages. Honestly, my impression was that names go all over
the map.
NAME-VERSION-RELEASE is "subtle"?
That's "interesting".
cgf 

Re: Please upload: doxygen-1.4.2_20050410-1 (n'th take)

[Christopher Faylor]

On Tue, Apr 19, 2005 at 10:30:12AM -0700, Hans W. Horn wrote:
>Max Bowsher wrote:
>>No, still wrong.  You didn't read what I said carefully enough.  You
>>*need* to understand:
>>Filenames are expected to be EXACTLY:
>>NAME-VERSION-RELEASE.tar.bz2
>>NAME-VERSION-RELEASE-src.tar.bz2
>
>I guess I never appreciated the subtle naming convention used for cygwin
>packages. Honestly, my impression was that names go all over the map.

NAME-VERSION-RELEASE is "subtle"?

That's "interesting".

cgf

Please upload: doxygen-1.4.2_20050410-1 (n'th take)

[Hans W. Horn]

Alright,
Max Bowsher wrote:
No, still wrong. You didn't read what I said carefully enough.
You *need* to understand:
Filenames are expected to be EXACTLY:
NAME-VERSION-RELEASE.tar.bz2
NAME-VERSION-RELEASE-src.tar.bz2
I guess I never appreciated the subtle naming convention used for cygwin
packages. Honestly, my impression was that names go all over the map.
Fixed (I think).
+++ doxygen_1.4.2-20050410/doc/language.doc +++
doxygen_1.4.2-20050410/doc/translator_report.txt +++
doxygen_1.4.2-20050410/examples/example.tag
These files are touched during a 'make install_docs'.
Excluded offending diffs from patch.
Same url (http://www.smithii.com/files/cygwin/hans/):
-rw-r--r-- 1 32237 ross 2273644 Apr 19 11:58 
doxygen-1.4.2_20050410-1-src.tar.bz2
-rw-r--r-- 1 32237 ross 1999837 Apr 19 11:58 
doxygen-1.4.2_20050410-1.tar.bz2
-rw-r--r-- 1 32237 ross 183 Apr 19 11:58 md5.sum
-rw-r--r-- 1 32237 ross 353 Apr 19 11:58 setup.hint

H. 

Re: Please upload: doxygen v1.4.2-20050410 (3nd take)

[Max Bowsher]

Hans W. Horn wrote:
Max,
Max Bowsher wrote:
Package naming still incorrect.
It should be:
doxygen-1.4.2_20050410-1.tar.bz2
doxygen-1.4.2_20050410-1-src.tar.bz2
Fixed.
No, still wrong. You didn't read what I said carefully enough.
You *need* to understand:
Filenames are expected to be EXACTLY:
NAME-VERSION-RELEASE.tar.bz2
NAME-VERSION-RELEASE-src.tar.bz2
VERSION is anything which begins with a digit, and does not contain a '-'.
RELEASE is a simple integer, starting at 1, incremented if there is a need 
to release a new Cygwin package of the same upstream version.


Also, please could you briefly describe the purpose and origin of the
following parts of the patch:
+++ doxygen_1.4.2-20050410/addon/doxywizard/version.cpp 1969-12-31
16:00:00.0 -0800
addon/doxywizard/version.cpp is created during the build and removed 
during
a 'make distclean'. The upstream version I was diffing against, must not
have been made 'distclean'.
I haved removed the offending file from the upstream version I am diffing
against!
OK.
+++ doxygen_1.4.2-20050410/doc/language.doc 2005-04-12
08:19:02.941256000 -0700
+++ doxygen_1.4.2-20050410/doc/translator_report.txt 2005-04-12
08:19:05.404798400 -0700
+++ doxygen_1.4.2-20050410/examples/example.tag 2005-04-15
08:12:16.622246400 -0700
These files are touched during a 'make install_docs'. diffs seem to be
meaningless! Is there a way to exclude them from the patch file (I mean
automatically)?
diff --help | fgrep exclude
The Cygwin-specific readme should be wrapped to remain within 80
columns.
Fixed! But, please, take a look at doxygen-1.2.18.README and tell me how
many chars per line you see!
And, by the way, the previous doxygen-1.2.18 version did ship with a pdf
version of its manual
A fresh start is a wonderful time to fix old bugs.
Max.

Re: Please upload: doxygen v1.4.2-20050410 (3nd take)

[Max Bowsher]

Corinna Vinschen wrote:
Is that ready to upload now?
No.
I'll reply to Hans' last mail with detail.
Max.

Re: Please upload: doxygen v1.4.2-20050410 (3nd take)

[Corinna Vinschen]

Is that ready to upload now?

Corinna

On Apr 15 16:51, Hans W. Horn wrote:
> Max,
> 
> Max Bowsher wrote:
> >Hans W. Horn wrote:
> >>I've uploaded another cut of doxygen v142 src & binary packages to
> >>http://www.smithii.com/files/cygwin/hans/, addressing more
> >>concerns/suggestions raised by Max Bowsher.
> >>In particular:
> >>1. removing pdf manual
> >>2. including upstream source tarball
> >>3. package naming issues
> >>[...]

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

Re: Please upload: doxygen v1.4.2-20050410 (3nd take)

[Hans W. Horn]

Max,
Max Bowsher wrote:
Hans W. Horn wrote:
I've uploaded another cut of doxygen v142 src & binary packages to
http://www.smithii.com/files/cygwin/hans/, addressing more
concerns/suggestions raised by Max Bowsher.
In particular:
1. removing pdf manual
2. including upstream source tarball
3. package naming issues
-rw-r--r-- 1 32237 ross 2276844 Apr 15 11:34
doxygen_1.4.2-20050410-src.tar.bz2
-rw-r--r-- 1 32237 ross 2000493 Apr 15 11:35
doxygen_1.4.2-20050410.tar.bz2
-rw-r--r-- 1 32237 ross 179 Apr 15 11:35 md5.sum
-rw-r--r-- 1 32237 ross 351 Apr 15 11:35 setup.hint
Does that do?
Package naming still incorrect.
It should be:
doxygen-1.4.2_20050410-1.tar.bz2
doxygen-1.4.2_20050410-1-src.tar.bz2
Fixed.
Also, please could you briefly describe the purpose and origin of the
following parts of the patch:
+++ doxygen_1.4.2-20050410/addon/doxywizard/version.cpp 1969-12-31
16:00:00.0 -0800
addon/doxywizard/version.cpp is created during the build and removed during
a 'make distclean'. The upstream version I was diffing against, must not
have been made 'distclean'.
I haved removed the offending file from the upstream version I am diffing
against!

+++ doxygen_1.4.2-20050410/doc/language.doc 2005-04-12
08:19:02.941256000 -0700
+++ doxygen_1.4.2-20050410/doc/translator_report.txt 2005-04-12
08:19:05.404798400 -0700
+++ doxygen_1.4.2-20050410/examples/example.tag 2005-04-15
08:12:16.622246400 -0700
These files are touched during a 'make install_docs'. diffs seem to be
meaningless! Is there a way to exclude them from the patch file (I mean
automatically)?

The Cygwin-specific readme should be wrapped to remain within 80
columns.
Fixed! But, please, take a look at doxygen-1.2.18.README and tell me how
many chars per line you see!
And, by the way, the previous doxygen-1.2.18 version did ship with a pdf
version of its manual
Re-uploaded!
-rw-r--r-- 1 32237 ross 2276504 Apr 15 19:45 
doxygen-1.4.2_20050410-src.tar.bz2
-rw-r--r-- 1 32237 ross 2000743 Apr 15 19:47 doxygen-1.4.2_20050410.tar.bz2
-rw-r--r-- 1 32237 ross   179 Apr 15 19:47 md5.sum
-rw-r--r-- 1 32237 ross   351 Apr 15 19:47 setup.hint

Does that do?
H.

Re: Please upload: doxygen v1.4.2-20050410 (3nd take)

[Max Bowsher]

Hans W. Horn wrote:
I've uploaded another cut of doxygen v142 src & binary packages to
http://www.smithii.com/files/cygwin/hans/, addressing more
concerns/suggestions raised by Max Bowsher.
In particular:
1. removing pdf manual
2. including upstream source tarball
3. package naming issues
-rw-r--r-- 1 32237 ross 2276844 Apr 15 11:34
doxygen_1.4.2-20050410-src.tar.bz2
-rw-r--r-- 1 32237 ross 2000493 Apr 15 11:35 
doxygen_1.4.2-20050410.tar.bz2
-rw-r--r-- 1 32237 ross 179 Apr 15 11:35 md5.sum
-rw-r--r-- 1 32237 ross 351 Apr 15 11:35 setup.hint

Does that do?
Package naming still incorrect.
It should be:
doxygen-1.4.2_20050410-1.tar.bz2
doxygen-1.4.2_20050410-1-src.tar.bz2
Also, please could you briefly describe the purpose and origin of the 
following parts of the patch:

+++ doxygen_1.4.2-20050410/addon/doxywizard/version.cpp 1969-12-31 
16:00:00.0 -0800
+++ doxygen_1.4.2-20050410/doc/language.doc 2005-04-12 
08:19:02.941256000 -0700
+++ doxygen_1.4.2-20050410/doc/translator_report.txt 2005-04-12 
08:19:05.404798400 -0700
+++ doxygen_1.4.2-20050410/examples/example.tag 2005-04-15 
08:12:16.622246400 -0700

The Cygwin-specific readme should be wrapped to remain within 80 columns.
Max.

Please upload: doxygen v1.4.2-20050410 (3nd take)

[Hans W. Horn]

I've uploaded another cut of doxygen v142 src & binary packages to 
http://www.smithii.com/files/cygwin/hans/, addressing more 
concerns/suggestions raised by Max Bowsher.
In particular:
1. removing pdf manual
2. including upstream source tarball
3. package naming issues

-rw-r--r-- 1 32237 ross 2276844 Apr 15 11:34 
doxygen_1.4.2-20050410-src.tar.bz2
-rw-r--r-- 1 32237 ross 2000493 Apr 15 11:35 doxygen_1.4.2-20050410.tar.bz2
-rw-r--r-- 1 32237 ross 179 Apr 15 11:35 md5.sum
-rw-r--r-- 1 32237 ross 351 Apr 15 11:35 setup.hint

Does that do?
H. 

Re: Please upload: doxygen v1.4.2-20050410 (2nd take)

[Max Bowsher]

Hans W. Horn wrote:
Max,
I found the origin of the mysterious "rendering problem" I'd referred to.
My computer is missing a font specified in doxygen.css:
.fragment {
font-family: Fixed, monospace;
font-size: 95%;
}
The doxygen pdf manual will go, as soon as I have found that friggen font
somewhere!
"monospace" is a generic family, which should work everywhere, and should be 
tried if "Fixed" cannot be found. So, it seems likely that you DO have a 
font called "Fixed", but it is broken and somehow causes all the characters 
to not appear.

Max.

Re: Please upload: doxygen v1.4.2-20050410 (2nd take)

[Hans W. Horn]

Max,
I found the origin of the mysterious "rendering problem" I'd referred to.
My computer is missing a font specified in doxygen.css:
.fragment {
font-family: Fixed, monospace;
font-size: 95%;
}
The doxygen pdf manual will go, as soon as I have found that friggen font 
somewhere!

H.
Max Bowsher wrote:
Hans W. Horn wrote:
Hi Max,
Max Bowsher wrote:
One further suggestion: I think it would be appropriate to include
only the html version of the manual. Including the PDF format too
substantially increases the size of the package, for no real gain -
it's just duplication.
Actually, I just noticed that there are rendering problems with the
doxygen
html pages for several browsers (IE, firefox) which don't occur with
the corresponing pdf.
So for the time being I'd prefer to keep the pdf!
I also noticed the same rendering problems with the doxygen html
pages on the web and posted about my observations on
gmane.text.doxygen.general.
I saw - however, I do not see the rendering problems displayed in your
screenshot in any of IE, Mozilla, or Firefox, so I am rather less
convinced about keeping the PDF.
Max. 

Re: Please upload: doxygen v1.4.2-20050410 (2nd take)

[Max Bowsher]

Hans W. Horn wrote:
Hi Max,
Max Bowsher wrote:
One further suggestion: I think it would be appropriate to include
only the html version of the manual. Including the PDF format too
substantially increases the size of the package, for no real gain -
it's just duplication.
Actually, I just noticed that there are rendering problems with the 
doxygen
html pages for several browsers (IE, firefox) which don't occur with the
corresponing pdf.
So for the time being I'd prefer to keep the pdf!

I also noticed the same rendering problems with the doxygen html pages on
the web and posted about my observations on gmane.text.doxygen.general.
I saw - however, I do not see the rendering problems displayed in your 
screenshot in any of IE, Mozilla, or Firefox, so I am rather less convinced 
about keeping the PDF.

Max.

Re: Please upload: doxygen v1.4.2-20050410 (2nd take)

[Hans W. Horn]

Hi Max,
Max Bowsher wrote:
One further suggestion: I think it would be appropriate to include
only the html version of the manual. Including the PDF format too
substantially increases the size of the package, for no real gain -
it's just duplication.
Actually, I just noticed that there are rendering problems with the doxygen 
html pages for several browsers (IE, firefox) which don't occur with the 
corresponing pdf.
So for the time being I'd prefer to keep the pdf!

I also noticed the same rendering problems with the doxygen html pages on 
the web and posted about my observations on gmane.text.doxygen.general.

H. 

Re: Please upload: doxygen v1.4.2-20050410 (2nd take)

[Hans W. Horn]

Hi Max,
Max Bowsher wrote:
Thanks! Some further issues:
In setup.hint, the first letter of an sdesc is typically capitalized
- just run setup.exe and look at the descriptions visible in the
package picker to see what other packages do.
Will fix at the next turn of the crank (if that's ok)!

The naming of the packages has a problem: Cygwin packages are
NAME-VERSION-RELEASE, of which only NAME may further "-" characters.
Since the upstream package contains a "-" within it's version,
changing this to a "_" would be a suitable workaround. Thus, the
binary package would be named: doxygen-1.4.2_20050410-1.tar.bz2.
Question: is the -1 at the end required? What is it supposed to mean? The 
release# under cygwin?
Anyways, I will change first '-' to '_' at the next turn of the crank!


A source package should be labelled with the addition of "-src", not
"_src".
Ditto.

Thanks for accomodating my request that the original upstream source
be included. It is more usual to include the upstream tarball itself,
though. Despite this being only an intermediate snapshot, it is
available as a tarball: http://www-kp3.gsi.de/~kp3softd/doxygen/.
Ditto

My name has no "c" in it. :-)
Oops.

One further suggestion: I think it would be appropriate to include
only the html version of the manual. Including the PDF format too
substantially increases the size of the package, for no real gain -
it's just duplication.
I never liked pdf docs, if I can use html docs instead. Will drop pdf docs 
at the next turn of the crank!

H. 

Re: Please upload: doxygen v1.4.2-20050410 (2nd take)

[Max Bowsher]

Hans W. Horn wrote:
Please upload the latest doxygen release for cygwin (v1.4.2-20050410)
Binaries, sources & setup.hint files are located at
http://www.smithii.com/files/cygwin/hans/
(thanks to Ross Smith II for providing web space).
-rw-r--r-- 1 32237 ross  2558933 Apr 12 20:18 
doxygen-1.4.2-20050410.tar.bz2
-rw-r--r-- 1 32237 ross  1824834 Apr 12 20:19
doxygen-1.4.2-20050410_src.tar.bz2
-rw-r--r-- 1 32237 ross  179 Apr 12 20:22 md5.sum
-rw-r--r-- 1 32237 ross  351 Apr 12 20:19 setup.hint

Since this is the 2nd attempt of my first contribution of this kind, 
please
bear with me
if I still didn't get it all right.

I honored various complaints by Brian Dessent and Max Bowscher.
Thanks! Some further issues:
In setup.hint, the first letter of an sdesc is typically capitalized - just 
run setup.exe and look at the descriptions visible in the package picker to 
see what other packages do.

The naming of the packages has a problem: Cygwin packages are 
NAME-VERSION-RELEASE, of which only NAME may further "-" characters. Since 
the upstream package contains a "-" within it's version, changing this to a 
"_" would be a suitable workaround. Thus, the binary package would be named: 
doxygen-1.4.2_20050410-1.tar.bz2.

A source package should be labelled with the addition of "-src", not "_src".
My name has no "c" in it. :-)
Thanks for accomodating my request that the original upstream source be 
included. It is more usual to include the upstream tarball itself, though. 
Despite this being only an intermediate snapshot, it is available as a 
tarball: http://www-kp3.gsi.de/~kp3softd/doxygen/.

One further suggestion: I think it would be appropriate to include only the 
html version of the manual. Including the PDF format too substantially 
increases the size of the package, for no real gain - it's just duplication. 
(This is a personal suggestion - it isn't part of established Cygwin 
policy - though perhaps we should actually make a Cygwin policy on this kind 
of issue).

Max.