Re: hacking broken ports
I was trying to build mplayer tonight, and I ran into a problem with net/liveMedia. The port that I've got calls for the build done on 10.24.2003. This file was unavailable on *any* of the listed mirrors, with the closest match being one built on 10.30.2003. I got around this problem by putting the file into /usr/ports/distfiles, and then modifying two files in /usr/ports/net/liveMedia; Makefile and distfile. I found that there was only on reference to the filename in the Makefile, so I changed it, and then I generated an MD5 on the file that I had and put it into distfile. After all of that foolishness mplayer built just fine. My question is this; am I on the right track, or am I going to screw something up if I keep using this slash-and-burn method? I'm new to FBSD (and *NIX), but this method seemed like it'd work. I'd just hate to do something that's going to bite me in the ass later on. No, this is just the way how ports are updated by their maintainers. Let me add some additional remarks: Before you fix/update a port you should check the GNATS data base if somebody has already released a patch (otherwise it would just be a waste of your efforts and time): http://www.freebsd.org/cgi/query-pr-summary.cgi?query The best thing would be -of course- if you read the Porter's Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ and shared your solution with others (i.e. fix the port for you and send a problem report). Also, what do I have to do to the permissions of /dev/dvd so that I can open a DVD in userspace. Right now I have to sudo mplayer to watch a movie, and that seems silly. Thanks. I suppose /dev/dvd is a symlink to one of your DVD drives. I think adjusting the group permissions (I believe you need rw for DVDs) for that device and putting you into the right right group should be fine. In general, I perfer granting access rights to a user group instead of running a process as root (even with sudo). Regards, Simon signature.asc Description: Digital signature
Re: hacking broken ports
The rest of your question has been answered, but: On Sat, 2003-11-01 at 23:00, William O'Higgins wrote: I found that there was only on reference to the filename in the Makefile, so I changed it, and then I generated an MD5 on the file that I had and put it into distfile. Instead of manually generating the MD5 and editing the distfile, you can fix the Makefile, delete the distfile, and do a make makesum and it will be built for you automatically. (Similarly, if for some reason the README.html has to be updated, just delete it an make readme.) Otherwise, you're on the right track. Also, in addition to checking that nobody's already submitted this, reading the Porting handbook, and submitting your fix via send-pr, you should probably email the package maintainer directly. In fact, you might want to do this first--it's possible the maintainer is about to do this, or has already tried and run into problems that she can tell you about before you hit them, etc.--and/or maybe she knows where you can get the previous version of the tarball. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
