mplayer from SVN
in [Ports]
|
From: Michal Varga on 29 Dec 2009 15:13 On Tue, Dec 29, 2009 at 9:03 PM, Sean C. Farley <scf(a)freebsd.org> wrote: > I am jumping randomly into the thread. > > If we want to use some type of "release" for MPlayer based upon a snapshot > from svn, how about using the same snapshot as used in Fedora (actually RPM > Fusion)[1]? Â It has the advantages of already being created, tested(?) and > easier to track bugs that users of Fedora may have already faced. > This is an interesting idea, though there may be one issue. Do we know how Fedora people create those snapshots? Let's say, hypothetically, there are two different output drivers in mplayer's SVN tree - let's name them CoolOutput_Linux and CoolOutput_BSD. Can we be sure that Fedora guys simply don't strip out the parts that they can't/will never use, so we end up with a snapshot package that lacks CoolOutput_BSD? m. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Sean C. Farley" on 29 Dec 2009 15:23 On Tue, 29 Dec 2009, Michal Varga wrote: > On Tue, Dec 29, 2009 at 9:03 PM, Sean C. Farley <scf(a)freebsd.org> wrote: >> I am jumping randomly into the thread. >> >> If we want to use some type of "release" for MPlayer based upon a >> snapshot from svn, how about using the same snapshot as used in >> Fedora (actually RPM Fusion)[1]? It has the advantages of already >> being created, tested(?) and easier to track bugs that users of >> Fedora may have already faced. >> > This is an interesting idea, though there may be one issue. Do we know > how Fedora people create those snapshots? Let's say, hypothetically, > there are two different output drivers in mplayer's SVN tree - let's > name them CoolOutput_Linux and CoolOutput_BSD. Can we be sure that > Fedora guys simply don't strip out the parts that they can't/will > never use, so we end up with a snapshot package that lacks > CoolOutput_BSD? In the source RPM, there is the script they use to generate the tar file. There are also a few patches in the RPM separate from the tar file. It looked like the tar file is missing a few pieces of libraries distributed separately. We probably already have (some of) them in the ports tree. I only glanced at the file; I did not inhale. :) Sean -- scf(a)FreeBSD.org
From: Thomas Zander on 30 Dec 2009 14:57 Hi Doug, Wes, list, On Tue, Dec 29, 2009 at 05:19, Doug Barton <dougb(a)freebsd.org> wrote: > B) I don't think "daily" is a reasonable target, but neither is "every > 3 years." This is correct. While it's true that I was hoping for the mplayer developers to change their minds and subscribe to a decent release engineering process, it seems it is not going to happen anytime soon. I was planning to switch the mplayer port to a svn snapshot some time next week (new year's resolution!) and continue with updated snapshot ports in the range of ~3 months or so. That is, if there is no objection from committers's perspective. @Wes: Would you mind sending me your modified port? TIA. Best regards, Riggs _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Wes Morgan on 30 Dec 2009 19:02 On Wed, 30 Dec 2009, Thomas Zander wrote: > Hi Doug, Wes, list, > > On Tue, Dec 29, 2009 at 05:19, Doug Barton <dougb(a)freebsd.org> wrote: > > > B) I don't think "daily" is a reasonable target, but neither is "every > > 3 years." > > This is correct. While it's true that I was hoping for the mplayer > developers to change their minds and subscribe to a decent release > engineering process, it seems it is not going to happen anytime soon. > I was planning to switch the mplayer port to a svn snapshot some time > next week (new year's resolution!) and continue with updated snapshot > ports in the range of ~3 months or so. That is, if there is no > objection from committers's perspective. I'll send it separately to those who have asked. Upgrading the mplayer and mencoder ports may not be as simple as a drop in. They require a newer version of x264, which there is already a pr for updating. I'm not certain about all of the dependencies, but there will be a shared library version to chase, and I believe that some ports may fail to detect it or even not compile. There is also the issue of the age of gcc in base. I use gcc44 from ports and enable the assembler in x264. It might just be my imagination, but I'm fairly sure my encodes get quite a few more fps on average. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Wes Morgan on 31 Dec 2009 00:39 On Tue, 29 Dec 2009, Lars Engels wrote: > Quoting Frank Staals <frank(a)fstaals.net>: > > > On 12/28/09 15:47, eculp wrote: > > > > > On Fri, 11 Dec 2009, Denis Shaposhnikov wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > Does anybody have a port for building mplayer from SVN? > > > > > > > > > > > > Thanks! > > On a sidenote: I used to build mplayer from svn regularly on my > > previous system. Updating mplayer usually was quite painless. Simply > > 'svn up && ./configure --prefix=/usr/local/mplayersvn && gmake && gmake > > install'. In 99% of the cases rebuilding went perfectly; no patches > > required or anything, and I rebuilded mplayer almost weekly. This was > > on a i386 system by the way, on my current amd64 install I run into > > problems trying to compile the current svn snapshots. > > > > I know it is not as nice as simply having a port. But if you realy need > > the svn-releases for some feature XYZ it may be a (temporary) solution. > > > Are there any killer features missing in our old version from ports? ffmpeg, x264 and mplayer/mencoder all have a number of improvements that are not available in official releases. x264 has some significant improvements with the mbtree option and I've seen quite a few bugfixes. There is also a remarkable speed improvement due to assembler, but this requires a recent version of gcc. Mplayer and mencoder have many bugfixes and they also handle blu-ray streams and codecs much better. Ffmpeg is also much improved in svn, especially with mpeg2 transport streams and the HD audio found on blu-ray/hddvd discs. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: CUPS/PAM configuration authentication problem. Next: deskutils/calibre build error |