11 Apr 2003 00:40
Best way to update gcc-wrapper
Shprentz, Joel [C] <ShprentzJ <at> nima.mil>
2003-04-10 22:40:53 GMT
2003-04-10 22:40:53 GMT
I finally upgraded to gcc--3.2.2 (from gcc--3.2) and realized that I needed to upgrade gcc-wrapper as well. I edited my team's package/gcc-wrapper.xml file to show the new version number in two places. Then I wondered how to deploy the change. First I tried ark package reveal --verbose gcc-wrapper but nothing happened. Ark knew that it had previously revealed this package. I found a clue in the automount-maps package description on "Sidai team: the `*-config' packages" page of the Ark web site: http://ark.sourceforge.net/sidai-config-pkgs.html. It said, When we make changes to the maps, we run sidai/package-utils/ark-invasive automount-maps to re-do things. Snooping around, I found this additional guidance on the "Sidai team: notes on booting ARK stuff" web page: http://ark.sourceforge.net/ark-boot.html. It said, ToDo: say something about `ark-invasive' ...? Well, nothing ventured, nothing gained. After examining ark-invasive and(Continue reading)
ark-invasive could easily be considerably improved. It's
presently just 'ark package uneverything ...' followed by
'ark package deploy ...'. As you've seen, that's often a
big hammer to crack a nut.
Alternatively, we could add a method (probably to
sidai/ark-vwrapped.xml), something like
'change-version-wrapper-version' that would do the business
directly.
Yell if you think there's some place we should add something
to some documentation...
Will
RSS Feed