[DRE-maint] Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

Antonio Terceiro terceiro at debian.org
Wed Mar 29 12:17:40 UTC 2017


On Wed, Mar 29, 2017 at 10:21:26AM +0200, Jonas Smedegaard wrote:
> Quoting Antonio Terceiro (2017-03-29 03:16:32)
> > That said, I am willing to support this, but I don't agree it's an RC 
> > issue.
> > 
> > I tried changing /usr/share/compass/frameworks/bootstrap-sass to 
> > /usr/share/compass/frameworks/bootstrap as you said, but that doesn't 
> > exactly make it work:
> [...]
> 
> > Any ideas?
> 
> Attached patch is what I use.  It might not apply as-is - I use it 
> together with a couple other patches to address the other issues 
> mentioned initially in this bugreport about the odd packaging into two 
> binary packages.

Ah, I see. this patch is needed to workaround the "old" Ruby
installation layout. Most Ruby packages nowadays, specially the ones
related to static assets, kind of assume the Rubygems layout, which is
supported by our tools, and could even be the default at some point.

If you need similar patches in all compass packages, you might be
interested in switching to the Rubygems layout. With that you just
symlink the Rubygems package location into the compass directory and
things just work. Something link this:

version = $(shell dpkg-parsechangelog -SVersion | cut -d - -f 1)

override_dh_auto_install:
	dh_auto_install
	dh_link -p compass-bootstrap-sass-plugin \
		/usr/share/rubygems-integration/all/gems/bootstrap-sass-$(version) \
		/usr/share/compass/frameworks/bootstrap-sass

That could even be modularized in a dh_compass_plugin or something like that.

I will upload a fixed version soon. Note however that the name of the package
is bootstrap-sass, and that -sass suffix is needed to make things just work.
Changing that would require renaming stuff under lib/, what would not be
sane. The correct usage is:

	compass create myproject --using bootstrap-sass


> Would you perhaps be interested in moving this package to the Sass team,
> and maintain the package there?  That helps coordinate the interaction
> between the Sass/Compass libraries (Compass is dead upstream, so there
> will likely soon be some restructuring to relax dependencies).
>
> I can also offer to take over maintenance of this package, if you don't
> mind that move but are not interested in joining that other team.

It's used by other Ruby packages, so I would rather have it stay in the Ruby
team.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20170329/48250abd/attachment.sig>


More information about the Pkg-ruby-extras-maintainers mailing list