Hi
Following up the discussion about making Pd64 ready for prime time, I wonder if there is or - if not - if we can make up a few best practices rules regarding the packaging of Pd64 compatible externals.
What I gathered so far:
* Package both floatsizes together. This allows to switch between Pd and Pd64 without having to re-install a package.
* Use the traditional suffix for floatsize=32, eg. ".l_amd64" so that older (floatsize=32) Pd versions still find their externals.
* Use new-style suffix for floatsize=64, e.g ".linux-amd64-64.so", that Pd64 tries it first, before it tries the "wrong" one with the traditional suffix.
* Don't pack too many archs and floatsize flavors in one package since the resulting filename might hit filename length limit of some filesystem (namely ecryptfs on Linux, but probably others as well)
* Dummy bullet point
Do those rules make sense? Are there any missing?
Then I wonder how to go about existing Deken packages. In order to add Pd64 support, I would like to upload an upstream version that has been already uploaded. If I add only the floatsize=64 flavor as a new package, I violate the first rule. It is ok to upload the same version again, but with both floatsizes? Should the old packages be deleted or will it be automatically overwritten? Or is it mandatory to bump the version?
Roman