Re: Oops, broke ncurses

On Tue, Nov 11, 2014 at 11:27:33AM +1300, Michael Homer wrote:
> On Tue, Nov 11, 2014 at 8:07 AM, Joel Roth <[email protected]> wrote:
> > Hi Jonas,
> >
> > Jonas Neumann wrote:
> >> SymlinkProgram ncurses $oldversion
> >
> > Thanks! However, SymlinkProgram aborts with a error:
> > /bin/bash: error while loading shared libraries: libncursesw.so.5: cannot open, not found
> >
> > I guess I can create the symlink manually...
> You can always perform the package management operations manually - in
> this case, `ln -sf /Programs/X/Y/lib/* /lib`, but copies and removes
> too. The tools are really only helpers. In this particular case though
> there is also RescueSymlinkProgram, a static executable, which will
> probably get you back up and running. You should run SymlinkProgram
> again afterwards.
> -Michael

Thanks, I booted from the iso, and, since I had problems
getting the paths right with RescueSymlinkProgram, I just
used rsync to copy the libncurses links from the iso
image.

Reminds me it may be a good time to back up the system!

For the recipes I've tried, one delicate part is the URL to
the tarball. For example, I needed to change the version
number to install the JACK audio connection kit. If I patch
a recipe, can I submit it to the archive?

An issue in creating *new* recipes is getting the dependency
information. I think instead of manually reading the build
docs for each app, it might be possible to to extract
dependency graph from another source, e.g. Debian, and
generate recipe stubs that will provide a reasonable first
approximation for dependencies, and possibly build
options.

And I'll close with one more question: is anyone thinking
about/working on an amd64 port these days?  I saw the porting doc ;-)

cheers,

Joel Roth