Hello All,

sorry I am writing again, but this time directly about this, and that is
raises this question that was not an issue until now, but I find it to be
very important for the stability of our project, as right now our repo, i.e.
some packages including the puredyne metapackage are broken. I would like to
raise the question of making our tree of packages independant of the Debian
Multimedia repository, the current problem being only one example for
answering -Yup- :-)
I know this would mean we'd have to make a huge amount of packages, I will
try and make a list of those that need to be debianized by us to compensate,
but the benefit of that work is  clear I think. We would have the control
over which versions of some really important libraries to use and could also
freeze those for a particular release. I would be willing to put some time
and effort to make this happen, maybe somebody else would want to chip in
too.

The second issue is something that I realised after poking around with jack
API and also in talking to robert_a on irc: we should contemplate providing
our own jack binary/library. The one in Debian (the latest stable release)
has a load of bugs that are fixed in svn, this also includes new
functionality.

Some packages that I can think of from top of my head:


   - ffmpeg / libavformat / libavcodec
   - cinelerra
   - avidemux
   - jack
   - ardour
   - mplayer
   - mencoder


Ultimately, I think, this will make our distribution much more stable and
dependable, as decisions made by the MM repo team (like renaming core
libraries) will not anymore affect us, requiring us to rebuild every
dependent package.

I'm really interested in everybodies opinion on this subject. If its a
no-go, let me know and I'll shut up :-) (but then no crying when our repo
breaks again!!!)

gre4t afternoon to everybody,

Karsten
---
[email protected]
irc.goto10.org #pure:dyne

Reply via email to