It might be better, easier and more useful to put this in a Homebrew formula. Homebrew seems the leading package manager on OS X today and I know where things end up (e.g. /usr/local). Furthermore I can inspect such a formula and verify it gets screen from a place I trust (an official GNU site or mirror) and inspect the patch so I know what it changes. Then you can provide the patch and you don't have to explain every time how people should invoke the patch command.
I built a Brltty formula a while ago which allows you to get the release or the latest development code. I never commited that to Homebrew due to some small problems including the Screen dependency and some configure errors with the release back then. I might dust that formula of if there is interest. Bram On 15-9-2014 22:35, Cheryl Homiak wrote: > On Sep 15, 2014, at 12:01 PM, Raoul <rm...@free.fr> wrote: >> here is, if you need it, a patched binary of screen-4.0.3. >> the command: >> tar zxvf screen403Patched.tgz will uncompress the archive. >> follow the README file to install, >> or copy files to their location. >> > I have a few questions and concerns. > > First of all, when you save this attachment, do not run the tar command > before you look at the README. This tar command doesn't just uncompress these > files into a directory but attempts to install them. I followed the command > in the email because it seemed to indicate this would just uncompress but > instead I ended up with these files with their paths in my home directory and > had to erase them. That might have been my own fault but this is how I read > the instructions in the email before I even got to the README; in fact, the > README wasn't available yet because it was in the zipped file. > > Second, I'm a little concerned as to why we have to change or replace > already-existing files in /usr/lib. I admit I don't know anything about this, > but is it necessary? I hesitate to change things on my Mac system unless I > know what I am doing and why I am doing it. Obviously, there must be a reason > but could you please give a simple explanation so I will know if I really > want to do this. Are the ncurses file and libSystem file specific to screen - > I don't think they are - and are we replacing them with some other version? I > haven't installed and tried this with brltty because I want to understanding > why I am doing this first. I'll install and try it once I understand this as > I can always go back to my already-installed and working screen-4.0.1. > > Finally, the REaDME has the command > > ln -s /opt/local/bin/screen-4.0.3 /opt/local/bin > > But I was thinking I wouldn't want to try to do a symlink with > /opt/local/bin. Wouldn't I do > > ln -s /opt/local/bin/screen-4.0.3 /opt/local/bin/screen > > It also may be necessary to make sure there isn't already an > /opt/local/bin/screen because if there already is one yu will be told that > screen already exists. > > Even if we have a binary, we still need the patch by itself or so it seems to > me. People set up their systems differently. For instance, I have screen in > /usr/bin. So some will want to compile and patch rather than having this > decided. > > > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
