cacti-plugin-arch patch: permanent url

[raiten]

i'm working on a port of cacti for openbsd with a flavor plugins. bsd are using a port tree with checksum on file.

actual distribution of plugin-arch is a tar.gz with patches for any releases of cacti and sometimes updates of a one-named patch which is not accepted by the port tree.

is there an url to download only one patch and be sure it will never change ? (else checksumming will fail)


thanks

[rony]

Not that I know of. But check with Jimmy (cigamit) on the forums for more detailed information.

[cigamit]

Nope, either I would have to update the url for version changes, and you would also never know what version of cacti it is for. Seems to be a weird requirement.

[raiten]

not that weird.
port tree infrastructure of *bsd (gentoo too, i suppose) download from products site (mirror on projects server) the files required to build a project.
before building, there is a checksum.

i don't ask main files to be split, but only to have a patch dir with permanent url for only a given release of cacti.

port tree (at least for openbsd) is only updated for last openbsd release.
so support for release n openbsd, i have cacti release m and arch m'.
as today, with cacti m+1, i have arch m'+1
so when you build cacti m on openbsd n, arch file would failed to checksum as latest file is m'+1, even if patch in the archive has not changed ...

of course, in openbsd N+1, you would get latest cacti and patch if maintainer has time to get it and got it committed.

finally, an easy solution for you would be
- keep http://cactiusers.net/downloads/plugins ... rch.tar.gz for main download
- and have something like http://cactiusers.net/downloads/plugins ... 2.patch.gz
for example

also, i check: when cacti has released a new version, the plugin-arch patch is fixed and never changed right ?
from time to time, i get a patch which change but i hope it's only for dev/rc release ?
(same reason as above, else checksum will fail)

thanks

[cigamit]

Hum... I will see what I can do. I actually use the same link, as the zip, tar.gz, tar files are generated on the fly using pure PHP when a new version comes out. Its then cached on disk, to save CPU.

I will have to manually upload the new versions for the patches, but I guess that isn't so bad.

[raiten]

thanks

[cigamit]

Every now and then I do actually push out a new version of the Plugin Architecture, even when Cacti didn't update. This is to add new hooks, or fix minor errors. Would you want me to add the PA version to it to also? For instance, the next version is 1.2 (actually I have a 2.0 that will be out eventually also, which is a major rewrite.).

cacti-plugin-arch_0.8.6j_1.2.tar.gz

What format is best for you?