2010/10/19 Felipe Sateler <fsate...@debian.org>:
> On Sat, Oct 16, 2010 at 11:09, Dan S <danstowell+de...@gmail.com> wrote:
>> 2010/10/6 Felipe Sateler <fsate...@debian.org>:
>>> Hi all, (Dan CCed because I'm not sure if you are subscribed to the list)
>>> I managed to take a few minutes to take a look at the package and it is
>>> not in a very good shape (it was still using simple-patchsys!). I have
>>> worked a bit on it, but it still has a long way to go. I will try to
>>> work on it during this week, I think I can find one hour or two.
>>> Dan, as you are part of upstream, could you comment on the patches
>>> included in the packaging? I can see they are in upstream svn ubuntu
>>> packaging module, with yourself as last commiter on most of them. They
>>> are older than the latest sc release, though.
>> Hi - sorry for slow reply, I missed this thread. Most of the patches
>> are by other people but I will try to comment:
>> 06_deb_scvim.diff
>>  - build machine != target machine so don't error out if no ruby executable
> This seems to also disable building scvim help?

Yes, but that's OK - it gets done on first run rather than on build.

>> 08_deb_scvim_checkactive.diff
>>  - the 'scvim' script is a wrapper which launches vim with the sc3
>> plugin. debian vim-addons policy requires the plugin not to be
>> auto-enabled when installing, so we must modify the scvim script to
>> detect if the addon is not enabled, and to help the user enable it if
>> they want to. (Needs to be a patch since vim-addon-manager not
>> necessarily used on all linuxes)
> The code seems to be appropriately protected. I think it can be safely
> incorporated upstream.

Good point. I've done that now in the svn.

> BTW, Dan, would you like to help maintain sc in debian? You could join
> our team, it is always good to have someone involved in upstream
> development.

Yes I would like to - thanks! Do I need an account somewhere? (On
git.debian.org I don't see much instruction...)


> --
> Saludos,
> Felipe Sateler

pkg-multimedia-maintainers mailing list

Reply via email to