From: Chandler Carruth <chandlerc@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for media-video/dvdrip
Date: Thu, 08 Dec 2005 17:59:28 -0500 [thread overview]
Message-ID: <4398BAD0.5040508@gmail.com> (raw)
In-Reply-To: <200512082047.58623.uberlord@gentoo.org>
I am not a gentoo developer, but a user, but I have submitted several
fixes for dvdrip in the past, and plan on continuing to use it, and get
it running and working in gentoo. I would be happy to maintain it, or
simply try to more responsively post fixes in the future to Bugzilla if
it would keep this package alive in portage. I think it is a very good
dvd ripping utility, and it _does_ work w/ transcode-1, the dvdrip
upstream developer simply still bases his work off of 0.6.x. He is
currently considering moving to transcode-1, so I doubt this package
will need to continue to be dependant on the difficult to manage
transcode version.
As a user currently, what steps could I take to help this package stay
alive? I will take them as the alternative is to put an unofficial
ebuild up on a webpage.
-Chandler Carruth
Roy Marples wrote:
>On Thursday 08 December 2005 20:23, Diego 'Flameeyes' Pettenò wrote:
>
>
>>On Thursday 08 December 2005 21:10, Mike Frysinger wrote:
>>
>>
>>>so the video herd policy is to remove packages until you're left with
>>>a small enough subset of packages you can handle ?
>>>
>>>
>>No, it's to remove the packages that have problems, that requires
>>dependencies that are badly broken (transcode 0.6 is a pain to manage, does
>>not work with GCC4 and it's not easily fixable, and upstream moved to
>>transcode 1), that requires maintenance and nobody can give it, and that
>>might be replaced by other programs with way less troubles...
>>
>>
>
>To be fair, you can hardly count GCC4 as it's not even in our unstable tree
>yet (and yes, I know it will be soon).
>
>Ya know, dhcpcd was in the same state. Unmaintained, didn't compile with GCC4
>and upstream was dead. Didn't hear any calls to remove it from the tree
>though as it was (and still is I suppose) the default dhcp client even though
>all the others are coded much better.
>
>
>
>>If you want to maintain that, no need for it to be removed... atm it's
>>going to be unmaintained in the tree, full of problems, and requires us to
>>not plan of dropping transcode 0.6.
>>
>>
>
>I have no wish to maintain it, but if it compiles then there is no need to
>remove it. So it's unmaintained - so was openvpn and net-misc/dhcp for pretty
>much a year or so until I stepped up.
>
>So if no-one steps up then let it sit in the tree if people are using it.
>
>Roy
>
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-08 23:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 17:42 [gentoo-dev] Last rites for media-video/dvdrip Diego 'Flameeyes' Pettenò
2005-12-08 18:08 ` Benoit Boissinot
2005-12-08 18:12 ` Chris Bainbridge
2005-12-08 19:46 ` Diego 'Flameeyes' Pettenò
2005-12-08 20:10 ` Mike Frysinger
2005-12-08 20:23 ` Diego 'Flameeyes' Pettenò
2005-12-08 20:47 ` Roy Marples
2005-12-08 22:59 ` Chandler Carruth [this message]
2005-12-10 0:14 ` Luca Barbato
2005-12-10 0:09 ` Luca Barbato
2005-12-10 2:19 ` Mike Frysinger
2005-12-10 5:13 ` Daniel Goller
2005-12-10 2:25 ` Donnie Berkholz
2005-12-12 3:32 ` [gentoo-dev] " R Hill
2005-12-14 4:58 ` Daniel Goller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4398BAD0.5040508@gmail.com \
--to=chandlerc@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox