← Back to team overview

openshot.developers team mailing list archive

Re: [Bug 421697] Re: OpenShot needs a flexible autotools-based installation script

 

I don't think this is valid anymore.  We use the Python setup.py distutils,
and do not package ffmpeg or mlt without code.  This was a complaint of the
old build wizard, I think.

On Thu, Sep 30, 2010 at 6:11 AM, moimael <moimael@xxxxxxx> wrote:

> Does this feature request always make sense ?
>
> --
> OpenShot needs a flexible autotools-based installation script
> https://bugs.launchpad.net/bugs/421697
> You received this bug notification because you are a member of OpenShot
> Developers, which is subscribed to OpenShot Video Editor.
>
> Status in OpenShot Video Editor: New
>
> Bug description:
> I'm really impressed by the OpenShot screenshots and screencasts, but
> current methods of installation are a real showstopper for me. When
> installing third-party programs, specially development versions, I want some
> flexibility that neither the build wizard and the debs give me.
>
> I would like to be able to at least specify the directories for both
> installation and libraries. Specifying a directory for libraries is
> particularly important to test with bleeding-edge versions of ffmpeg and mlt
> avoiding any conflicts with programs compiled for old versions (such as
> kdenlive).
>
> The best course of action would be to use autotools.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openshot.developers
> Post to     : openshot.developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openshot.developers
> More help   : https://help.launchpad.net/ListHelp
>

-- 
OpenShot needs a flexible autotools-based installation script
https://bugs.launchpad.net/bugs/421697
You received this bug notification because you are a member of OpenShot
Developers, which is subscribed to OpenShot Video Editor.

Status in OpenShot Video Editor: New

Bug description:
I'm really impressed by the OpenShot screenshots and screencasts, but current methods of installation are a real showstopper for me. When installing third-party programs, specially development versions, I want some flexibility that neither the build wizard and the debs give me.

I would like to be able to at least specify the directories for both installation and libraries. Specifying a directory for libraries is particularly important to test with bleeding-edge versions of ffmpeg and mlt avoiding any conflicts with programs compiled for old versions (such as kdenlive).

The best course of action would be to use autotools.





References