Dixi quod…
Fabian Greffrath dixit:
Yep, from the next upload on it is.
Actually, not even that is needed. I just took the current git HEAD,
versioned it lower than the current sid package, dropped all the
unnecessary B-D for bootstrapping from debian/control, and will
upload that to
Fabian Greffrath dixit:
Yep, from the next upload on it is.
Actually, not even that is needed. I just took the current git HEAD,
versioned it lower than the current sid package, dropped all the
unnecessary B-D for bootstrapping from debian/control, and will
upload that to debian-ports.org
On Thu, Jun 21, 2012 at 10:30 AM, Thorsten Glaser t...@mirbsd.de wrote:
Fabian Greffrath dixit:
Yep, from the next upload on it is.
Actually, not even that is needed. I just took the current git HEAD,
versioned it lower than the current sid package, dropped all the
unnecessary B-D for
Reinhard Tartler dixit:
AFAIUI, the yasm package should be available on any architecture. You
can build libav without it, but you'll miss a number of important
architecture specific optimizations. For m86k, I doubt that there are
Yes, it’s installable – but a quick grep shows it’s only used
in
Am 21.06.2012 12:36, schrieb Reinhard Tartler:
AFAIUI, the yasm package should be available on any architecture. You
can build libav without it, but you'll miss a number of important
architecture specific optimizations. For m86k, I doubt that there are
any, so I'm confident that you can drop
Am 19.06.2012 18:46, schrieb Thorsten Glaser:
Ah, we’re really getting things like that? Nice!
It is a proposed extension to the debian/control file that is not yet
accepted AFAICT. This is why I put it in README.source and not
directly in debian/control.
Great, so a bootstrap libav
Fabian Greffrath dixit:
Great, so a bootstrap libav should be decently easy.
Yep, from the next upload on it is.
Ok, thanks a lot. I’m still working on other packages like pygtk,
so no need to hurry for me.
bye,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it
On Mon, Jun 18, 2012 at 9:27 PM, Thorsten Glaser t...@mirbsd.de wrote:
Hi,
m68k currently has no libpostproc-dev and friends, built from src:libav.
How do you recommend to bootstrap this, considering several (at least
four) build dependencies of libav, all codecs or something like that,
Am 19.06.2012 09:18, schrieb Reinhard Tartler:
I'm a bit confused now. libav itself does not build depend on
libpostproc-dev, and if it did, then that would be a bug IMO.
I believe this issue is not specific to libpostproc, but with
libpostproc-dev and friends the OP meant library packages
On Tue, Jun 19, 2012 at 9:38 AM, Fabian Greffrath fab...@greffrath.com wrote:
Am 19.06.2012 09:18, schrieb Reinhard Tartler:
I'm a bit confused now. libav itself does not build depend on
libpostproc-dev, and if it did, then that would be a bug IMO.
I believe this issue is not specific to
Am 19.06.2012 09:46, schrieb Reinhard Tartler:
Currently, libx264 and gpac use that, but opencv only in ubuntu (I
need it there because all of those are not in main, and I want to keep
the differences minimal). I'll switch opencv as well in the next
upload.
Maybe we should leave a note in
On 12-06-19 at 09:59am, Fabian Greffrath wrote:
Am 19.06.2012 09:46, schrieb Reinhard Tartler:
Currently, libx264 and gpac use that, but opencv only in ubuntu (I
need it there because all of those are not in main, and I want to
keep the differences minimal). I'll switch opencv as well in the
Fabian Greffrath dixit:
and friends the OP meant library packages built from libav sources in
general.
Yes.
Thorsten, that's three circular build-dependencies. Which one is the fourth
one
that you mentioned in your report?
frei0r, via some corners, too.
Anyway, all of these codecs are
Am 19.06.2012 13:45, schrieb Thorsten Glaser:
frei0r, via some corners, too.
Ah, I see:
libav - frei0r - opencv - libav
Am 19.06.2012 12:35, schrieb Jonas Smedegaard:
What would be even better is to add a hint to control file which exact
packages can be skipped to generate a
Am 19.06.2012 13:45, schrieb Thorsten Glaser:
Reinhard Tartler dixit:
Well, I take that as another reason to use the cond_enable macro in
debian/confflags for these libraries, because this way you do not even
have to edit any file, but can just bootstrap with 'dpkg-buildpackage
-d -b'.
I have
On Tue, Jun 19, 2012 at 4:14 PM, Fabian Greffrath fab...@greffrath.com wrote:
Am 19.06.2012 13:45, schrieb Thorsten Glaser:
Reinhard Tartler dixit:
Well, I take that as another reason to use the cond_enable macro in
debian/confflags for these libraries, because this way you do not even
have
Fabian Greffrath dixit:
Am 19.06.2012 12:35, schrieb Jonas Smedegaard:
What would be even better is to add a hint to control file which exact
packages can be skipped to generate a crippled-but-usable-for-rebuild
package. I forgot what that hint is called or its syntax (even if I was
at the
Hi,
m68k currently has no libpostproc-dev and friends, built from src:libav.
How do you recommend to bootstrap this, considering several (at least
four) build dependencies of libav, all codecs or something like that,
build-depend on libav’s binaries again? Can libav be built without any
of those
18 matches
Mail list logo
