On, Wed Sep 03, 2014, Thierry Thomas wrote: > Le mer 3 sep 14 à 21:12:56 +0200, Marcus von Appen <[email protected]> > écrivait : > > > On, Wed Sep 03, 2014, Bryan Drewery wrote: > > > [...] > > > > > I understand there is fear involved with not having a plist validate > > > everything. Consider that many other package systems do not require a > > > plist to start. > > > > [...] > > > > Seconded. In my opinion for 95% of all cases it sums up to: everything in > > the > > staging directory gets installed. We can use post-build or pre-install to > > clean up the staging directory where necessary, or even revert the plist > > meaning in the worst case, e.g. everything in ${EXCLUDE_INSTALL} is not to > > be > > installed, if necessary. > > I disagree. I use plist for two things:
You belong to the +-5% ;-). > - when upgrading a port, I compare the previous plist with the newer > one, and if some important files are missing, I try to understand the > reason; For those things a comparision mechanism in the qa scripts for a porter/committer might come in handy: - get stagedir contents - get (current) package contents - compare and show a list of changes for the QA > - I often grep all plists to find which port could possibly provide such > header or such library (among non-installed ports, of course). I do the same, but would argue that such a query service should belong to or offered by a pkg search (as sort of counterpart to pkg which). Cheers Marcus
pgp6T7gbmNik2.pgp
Description: PGP signature
