Mike Gerdts writes: > I'm not saying that Solaris is wrong or that you are wrong from a > purely technical standpoint - it is a matter of making it easier for > new developers to provide packaged software for Solaris.
My argument is that if they have to do anything substantial by way of scripts, then either they don't understand how packaging works, their software has problems, or something is just horribly wrong with the packaging system itself. That should not be so. The cases where people have to do this are fairly narrow, and usually involve updates to configuration files. With well-designed and well-controlled software, that shouldn't be much of an issue -- don't break your configuration file syntax and you won't notice. > People that come from other platforms where /bin/sh implements a fair > amount beyond what POSIX says will have troubles with the Solaris [...] > broken in strange and frustratingly unexpected ways. This was a hard > lesson to learn because I came to Solaris from other platforms. Yes; understood. > What happens when ksh93 is integrated? Does /bin/sh become ksh93? It No. The project team hasn't proposed doing that yet. It's plausible. The incompatibilities (and how they'll be handled) need to be worked out. > seems as though this would open the door for people to develop > packaging scripts on Solaris.next that don't run on Solaris.previous. > (Hmmmm... another question for arc-discuss, likely.) That'll lock a number of users out of upgrade scenarios. I think it'd be good to avoid it unless there's a very clear _need_ to do this. > Just out of curiosity, does anyone know why the packaging scripts > ignore the sha-bang line? I understand they are explicitly called > with /bin/sh or /sbin/sh, but why was that decision made? Is this a > lesson that shouldn't be unlearned? I think the operation dates to AT&T. In any event, I don't think this is really the right angle to attack. Improving something that for decently stable software ought not exist seems like a losing proposition. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
