Did the email I sent out on the 1st not not make it to the group? I
already put forward many of the issues that Vassili is talking about.
Here's the email. Feel free to delete, of course.
--------------
I'd like to put forward a few ideas for the userland application
install:
Currently, using a single home directory to access multiple
architectures is complicated by a number of factors:
- operating system (Solaris, Linux, HP-UX, etc.)
- Different revisions of operating system (Solaris 8-10, etc.)
- cpu architecture (sparc vs x86)
- word size (32 vs. 64 bit)
- application version (some apps aren't available for all systems)
Historically, I've fixed this as an administrator by using the
automounter and symbolic links:
vim -> vim-6.4 (in the user's path)
In automount map:
vim-6.4: server:/export/apps/&/${CPU}/${OSNAME}${OSREL}
While this works, I think only the largest sites will have
implemented something similar.
What I'd like to see would be the ability to install vim at a user-
level into my home directory and have my home directory work
transparently on multiple architectures.
I think it could work if it can be designed properly up front:
Use the above information when storing the packages:
$PATH += $HOME/applications/`uname -s`/`uname -r`/`mach`/bin
$MANPATH += $HOME/applications/`uname -s`/`uname -r`/`mach`/man
$LD_LIBRARY_PATH += (similar stuff)
etc.
The package file could exist anywhere appropriate, perhaps
$HOME/.packages. It may also be practical to move applications
to .applications.
If the above could be implemented, it would address most of the above
issues.
It still wouldn't address multiple versions of an application, but
that may no longer be necessary if the different versions are
required only for different architectures.
I'd personally like to be able to install gnu find (it supports case-
insensitive searching) and vim for all architectures in my home
directory, and using something like the above would allow me to
install packages into my home directory for multiple architectures
without a lot of complexity.
The ability to track and update these packages would be a very
helpful situation from a user perspective.
--------
On Jun 6, 2006, at 9:14 AM, Vasiliy wrote:
> I talk to Bart and he raise serious consern about installation in
> $HOME or any shared area (he asked me to post it here). Home
> directories srared over network and can be accessible from any
> architecture and any Solaris Version. So instalation of software in
> shared area need special attention and special procedure to make it
> multiplatform.
>
> I think that Shared Software is another big project. It is obvoius
> that certain software can not be installed this way as well as that
> some software can be installet with automount option which choose
> right architecture etc... However Personal Install need to address
> this issue somehow.
>
> Thanks, Vassili.
>
>
> This message posted from opensolaris.org
> _______________________________________________
> install-discuss mailing list
> install-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/install-discuss
-----
Gregory Shaw, IT Architect
Phone: (303) 673-8273 Fax: (303) 673-2773
ITCTO Group, Sun Microsystems Inc.
1 StorageTek Drive ULVL4-382 greg.shaw at sun.com (work)
Louisville, CO 80028-4382 shaw at fmsoft.com (home)
"When Microsoft writes an application for Linux, I've Won." - Linus
Torvalds
