It seems that all the split distributions of Schily's tools have been replaced by a single huge schily-tools tree . After reporting a bug to star, the author told me to use the latter. I suppose we'll need to migrate all our packages to them then, and figure out how to version and build them sanely.
The schily-tools exist for quite some time now. It just seems smake, star and cdrtools are not released separately any more.
If I remember correctly I tried to build from the schily-tools but eventually gave up.
Versioning should not be a problem, we can just use the release date can't we? Building all this stuff sanely will be the bigger issue.
By versioning, I meant we'd have to check whether the new version includes any (possibly indirect?) changes to the tool in question.
Schilytools exist since December 2007.
Since it is hard to create frequent separate releases for various tools, it is easier to mostly concentrate on one consistent release of schilytools.
Platforms that like to install the libraries from the schilytools as shared libraries need to use schilytools anyway since this is the only way to maintain consistency in the library versions.
Note that there recently has been a need to introduce incompatible library changes in libfind and libschily thsat resulted in a new major version for these libs.
*** Bug 678914 has been marked as a duplicate of this bug. ***
*** Bug 678918 has been marked as a duplicate of this bug. ***
Martin Väth already put some effort in creating an ebuild for schily-tools.