Dave Miner wrote:
Darren Reed wrote:
Dave Miner wrote:
Darren Reed wrote:
Bart Smaalders wrote:
Philip Brown wrote:

When the smarts are shifted to "the packaging *system*", it allows that the package itself, be 'dumber', as far as explicit system knowledge goes. It allows for the package to specify function, rather than mechanism.
This is a good thing.

Let's take a case in point.  Various packages deliver fragments of
/etc/security/exec_attr.  We could make pkg(5) know how to stitch
those together, and write a new services file - and deal w/ upgrade
issues when the format changes, including back-publishing versions of
IPS that can write the new format to all previous releases of Solaris
from which we want to upgrade. Or we could tell package developers to place their file fragments in a well-known directory, and tag the file
as requiring the refresh of a well-known service.  The latter will
work just fine across upgrades, and the well-known service can take
care of reading legacy format file fragments from older packages, etc.

This sounds nice but what will the implementation
of this be?

If we move towards a design where there is an FMRI
that looks after each file, are we going to end up
with countless more FMRIs that are just for massaging
these files?


Countless? Doubtful. I'd put the upper bound at a few dozen. There really aren't that many of these types of files.
conversion utility.

Just as a point of fact...

If this is what's done to replace all the "e" file type from SVR4 packages then:
$ egrep '^e ' $SRC/pkgdefs/SUNWcsr/prototype_com | wc -l
93

$ egrep '^e ' $SRC/pkgdefs/*/prototype_com | wc -l
    237

However...

$ /bin/ls -1 $SRC/pkgdefs/common_files/i.* | wc -l
     90

$ /bin/ls -1 $SRC/pkgdefs/*/i.* | wc -l
     96

... so it would seem that the target is a little bit more than a few dozen, but perhaps not more than 100.

And I haven't looked at the files in detail to know how many of the above can be excluded.


And so I'll stand by my estimate, which is way less than the fear-mongering "countless" you posited to start with. Always nice to work from real data, isn't it?

Well I'll admit that the "countless" was a (deliberate) exageration to try and draw attention to the point I was making.

And yes, it is.

Darren

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to