I think right way to define packages is DU created not for one file but for set of files which represents certain "service". This "service" is not formal definition so it allows as some flexibility to define packages in reasonable practical way. For example we may have service "Standard Unix Utilities" which will include ls, cat, grep, etc...
However with non formal definition of services, which combines some files in a set, after this done it is pretty clear what need to be done to create DU for it - how to make package for this service so this service then can be delivered independently from other unrelated independent services, but with all other necessary packages this one depends on. vassun This message posted from opensolaris.org
