#16733: Tidy Update Request ------------------------------------+--------------------------------------- Reporter: william.dinoia@… | Owner: ryandesign@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Keywords: tidy update request | Port: tidy ------------------------------------+--------------------------------------- Comment(by sierkb@…): Replying to [comment:3 ryandesign@…]:
Actually it looks like they're not assigning version numbers or more importantly tags in CVS.
Since the system for automatically providing source and binary packages on http://tidy.sourceforge.net/ is broken, the Tidy/TidyLib project does NOT have an official versioning scheme, so the CVS HEAD version is always the latest stable available version. The official "version number" of tidy/tidylib is in tidy/src/version.h and is allways a date (currently the string "7 December 2008") -- the date, when the latest change has been made to the tidylib itself. That does NOT cover other changes, that could have been made in the meantime to other source files belonging to tidy resp. tidylib. These possibly other changes to other source files are only covered, if you make a CVS HEAD checkout.
That means we cannot pull from CVS and reliably get the same build each time.
Maybe you can stick to one specific version stamp, meaning the date string of /tidy/src/version.h and search for it, while checking out from CVS (if this is a possible way to go).
We will have to make our own source packages and host them at MacPorts.
Maybe that is the one and only possibility to be up-to-date. And regulary update tidy on MacPorts by pulling the latest CVS HEAD update from the tidy trunk. Others, like some Linux distributors, do so as well. -- Ticket URL: <http://trac.macports.org/ticket/16733#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS