[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Distributed *.deb

>>>>> "Jim" == Jim Pick <jim@jimpick.com> writes:

Jim> Perhaps it might be cleaner, but more complicated to build into
Jim> dpkg, if dpkg could be made aware of "status" files on remote
Jim> servers (on read-only filesystems) and it could "install" the
Jim> remotely installed packages by inserting symlinks into the
Jim> filesystem.

A solution for a substantially smaller problem would be if dpkg (like
rpm) had a notion of `netshared path', ie. that it could recogninze
certain paths (for instance /usr/share) as something that was not a
local filesystem but mounted from somewhere else. 

The implication is that it should not try to mess with files on
netshared paths. If a package wants to install to files, one in
/usr/bin and one in /usr/share (and /usr/share is netshared), it would
only actually install the file to reside in /usr/bin.

I don't know that much about how rpm handles it in details (and there
is of course tons of details to sort out, and I know that the rpm
implementation is all but flawless).

At least our system is a quite complicated mess of things being local
or NFS mounted depending on both machine type and disk configuration.

Am I mistaken about dpkg not having strategies for dealing with
parts of the filesystem being readonly NFS mounted?

Christian Lynbech          | Computer Science Department, University of Aarhus
Office: R0.32              | Ny Munkegade, Building 540, DK-8000 Aarhus C
Phone: +45 8942 3218       | lynbech@daimi.aau.dk -- www.daimi.aau.dk/~lynbech
Hit the philistines three times over the head with the Elisp reference manual.
                                        - petonic@hal.com (Michael A. Petonic)

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: