[Ffmpeg-devel] Specific revisions from CVS

Barry Cooper cooperb
Thu Sep 8 22:14:09 CEST 2005

> There may be an easier way, but this works:
> mkdir tmp
> cd tmp
> cvs -z9 -d:pserver:anonymous at mplayerhq.hu:/cvsroot/ffmpeg co -l ffmpeg
> cvs -z9 -d:pserver:anonymous at mplayerhq.hu:/cvsroot/ffmpeg co -r 1.81 
> ffmpeg/Makefile

Thanks, this is good. Trying it, I see that the first cvs command gets 
me the current release where the second line simply overwrites the 
Makefile with a previous version.

> Please do not use REPLY-TO to post the 1st message of a thread, the 
> net result is subjects mixed in the same thread, which BTW reduces the 
> likelyhood of you getting an answer...

I'm a mailing list virgin, sorry.

>> I want to apply a patch to some ffmpeg source so i may compile it to 
>> give me a standalone shared binary library on OSX. It seems the patch 
>> only operates on, for instance, release 1.8.1 of ffmpeg/Makefile.
> I hope your goal is to port the patch to 1.83?

No, that's a bit beyond me right now. But it's a nice thought, with a 
little assistance I'd like to try. I'm actually trying to apply the 
patches that allow ffmpeg to be compiled on osx to produce a shared 
libavcodec.so file - patches posted on this mailing list about 6 weeks 
ago that unfortunately, require 1.81. Ultimately I want to compile 
transcode (which requires libavcodec.so).

>> I am having trouble getting this from cvs, i can only manage to get 
>> version 1.8.3 (the current one).
> Its 1.83. Try to post accurate info.

Sorry again.

>> I presume i need some variant on the following:
>> cvs -z9 -d:pserver:anonymous at mplayerhq.hu:/cvsroot/ffmpeg -r r1_8_1 
>> co Makefile
> Always copy/paste commands you use, never retype. Such a command is 
> rejected with "Unknown command: `r1_8_1'" so that's certainly not what 
> you tried.

Assumptions are not great things at the best of times. Actually, I did 
copy it and that is indeed what I typed. Believe it or not, I spent a 
considerable while searching google for "cvs specific revision" in 
order to work out how to get something other than the current revision. 
The man page was a little confusing. The best thing I could find was 
another sourceforge project's site and their instructions for getting a 
previous revision was in the above format. it was the best I had, so I 
tried it but to no avail. I thought it would be better to show you that 
than say "I tried getting a previous revision but it didn't work" as 
the response would have invariably been "Show us what you typed" and 
"what was the resonse".

> Michel Bardiaux
> R&D Director
> T +32 [0] 2 790 29 41
> F +32 [0] 2 790 29 02
> E mailto:mbardiaux at mediaxim.be

I have to say, Michel, I find your aggressive tone a little uncalled 
for. I apologise for my ignorance but in my defence:

- I am not a unix virgin, neither am I stupid.
- I am also, however, not a unix guru. I am here for fun.
- I didn't think the "user" mailing list was the place the post 
compilation questions.
- I have spent a lot of time in the last week searching the interweb 
for clues rather than jump in on a mailing list and waste people's time 
with a newbie question to be found in a FAQ. But at the end of the day 
I was a little stuck and thought, mailing lists are here to allow 
people to share their knowledge, so sent my question.

I would gladly improve my shell script knowledge and update these 
patches (if I get them all to work) to the latest release. Hey, I'd 
even like to help people verify their code compiles on osx (we 
darwiners seem to be in a minority. or at least a vocal minority). 
Anything to do my bit for the open source community, I use enough of 
the software, I should contribute somehow.

But you dudes will need to chill out a little, please.

Suggestion - another mailing list for complilation / compatibility 
issues (as I am clearly not a coder by day nor night)?
Or how about a decently detailed faq to keep plebs like me off your 
mailing list?



More information about the ffmpeg-devel mailing list