Hi there,
Am Montag, den 01.05.2017, 21:42 -0700 schrieb Nishanth Aravamudan: > Package: sassphp > Version: 0.5.10-2 > Severity: normal > > It would appear that sassphp doesn't follow many other PHP packages > and > explicitly names it's binary package php7.0-sassphp rather than > php-sassphp. This requires renaming the binary package and explicitly > adding transitional changes for upgraders as the PHP version changes. I've ssen both name schemata being used and wasn't able to figure out a pattern behind it unfortunately, and didn't find a documentation along the lines unfortunately. There are also many other PHP packages that start with php7.0-*, and unfortunately I settled for the wrong naming scheme. On the other hand, given that the package only lives in unstable I don't see the need for a transitional package. It wasn't part of any release and thus I think adding the complexity isn't needed. Users of unstable are meant to be able to deal with such things. > Can sassphp be modified to be like other PHP packages and generate > php-sassphp? Sure. Can you maybe point me to the documentation on that guideline so I can avoid it in the future? I really looked at the package in the pool, couldn't figure out what the default schema is meant to be, asked around ... Mistakes happen, so very much thanks for your report and the possibility to fix this. :) Enjoy, Rhonda
signature.asc
Description: This is a digitally signed message part
