Rich McAllister wrote: > Dave Miner wrote: > >>> >>> If the home directory is on an nfs share the system admin might not >>> be able to access it. The user might use the machine never again, and >>> prefers to use a different one to deinstall his software (or move it >>> to the trash can on a Windows box). >>> >> >> Sorry, that sounds like we're just trying to say ETOOHARD, and I don't >> buy it. For these cases, we can construct all sorts of cross-system >> solutions, perhaps using a directory service, as you sort of seem to >> allude to. Solving that would seem to be even more valuable, because >> then you can help improve TCO of a larger "system". > > This project will certainly fail if it requires installations to deploy > some network-wide repository prior to installing any software. If we > tell developers the way to try, say, Studio Creator is > > 1. Download this file. > 2. Get your system administrator to deploy a Solaris 10 > server running Sun Java N1 Grid Software Repository Server 2.3 > or later > 3. Run the file you downloaded in step 1 > > then our prospective developers will suddenly discover that BEA, > WebSphere, and/or .NET suits their needs pretty well after all. >
I think you're way over-interpreting my comments. There are customers for whom the above is undoubtedly uninteresting, but I believe there are many for whom it is, and so I'd like us to give it some thought before plunging ahead. The proposal is to massively expand the usage of packaging without any thought to the administrative burden that might result, and I just don't think that's right. We know these problems exist, and we've punted on them. We might even decide to punt on them again, but to argue that we shouldn't even consider it is just inconceivable to me. Dave
