[Pkg-sass-devel] Bug#817139: Bug#817139: sassc: trying to overwrite '/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1

[Frederic Bonnard]

> The name "sassc" means "Sass implemented in C".
> 
> Since the package name "pysassc" seems to imply "sassc wrapper 
> implemented in Python", I believe the proper fix here is for pysassc to 
> not provide binary "sassc" but instead "pysassc".

right

> ...or simply drop the package pysassc, because there should be no need 
> for that wrapper on systems where the real sassc is available.

sure ; but I'd prefer to let users choose.

Actually one of the project I use, needed as a build-dep sassc from
python-libsass, because as many python projects they drag build-deps with pip
and don't bother with original C projects with native tools.

And the latter has specific options also, different from the one from sassc
package with is embarassing for dependant projects.
I see 3 possibilities :
- we remove sassc from python-libsass but we'll have to do something for
  projects using it as build-deps.
- we rename sassc in python-libsass pysassc, same point.
  In both last 2 points, we could see with upstream libsass-python if they can
  do the same on python sassc script to prevent more deb/ work to patch other
  projects depending in python sassc, but it's unsure they'll follow.
- or I put in python-libsass's control an exclude with sassc

Last point would be the least work solution on all sides, and that'd be up to
users to choose if they want the "real" sassc or the pythonic one.
Any thoughts ?

Fred