#16733 closed update (fixed)
Tidy Update Request
| Reported by: | william.dinoia@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch | Cc: | sierkb@…, blb@…, nox@… |
| Port: | tidy |
Description
Requesting the tidy port be updated to a more current version.
Attachments (2)
Change History (14)
comment:1 Changed 16 years ago by jmroot (Joshua Root)
| Owner: | changed from macports-tickets@… to ryandesign@… |
|---|
comment:2 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
| Status: | new → assigned |
|---|
comment:3 follow-up: 5 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
Actually it looks like they're not assigning version numbers or more importantly tags in CVS. That means we cannot pull from CVS and reliably get the same build each time. We will have to make our own source packages and host them at MacPorts.
comment:5 Changed 16 years ago by sierkb@…
Replying to 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.
comment:6 Changed 16 years ago by jmroot (Joshua Root)
| Type: | enhancement → update |
|---|
comment:8 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
I had forgotten that using CVS we can also specify a checkout based on a date. There are other ports that do this. So I can do the same for tidy and thereby save myself the inconvenience of having to regularly package up tarballs and upload them to the distfiles area of the MacPorts repository.
comment:9 Changed 15 years ago by blb@…
| Cc: | blb@… added |
|---|
Attached is a patch to update tidy to 20090315 (from FreeBSD's mirror); passes the testall.sh test script.
Changed 15 years ago by nox@…
| Attachment: | tidy-20090325.diff added |
|---|
comment:10 Changed 15 years ago by nox@…
| Cc: | nox@… added |
|---|---|
| Keywords: | haspatch added; tidy update request removed |
| Version: | 1.6.0 |
Another patch to 20090325 using gentoo mirrors added in r62395
comment:11 Changed 15 years ago by nox@…
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Maintainer timeout, r62538
comment:12 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Thanks; sorry for my non-responsiveness. Feel free to add yourself as maintainer or take over entirely.
They aren't releasing distfiles anymore; we'll have to switch to pulling the source from CVS.
Since this will pull in many years worth of updates, we should be careful to test tidy's dependents for any breakage with the new version. Currently that would be php5/php5-devel, bluefish, py-utidylib/py25-utidylib and py25-mx-experimental.