base-files request

[Morrison, John]

Igor Pechtchanski wrote:
> On Mon, 21 Jun 2004, John Morrison wrote:
>>> From: Igor Pechtchanski
>> done < base-files-manifest.lst
>          ^^^^^^^^^^^^^^^^^^^^^^^
> Shouldn't this be "/etc/preremove/base-files-manifest.lst"?

humm, prob, I didn't know where the script was run from, but
a full path would make that redundant.

> Also, why not simply

erm, cause I didn't know how? ;)

My scripting capabilities are not really *that* good, I just
hack up something which works; which is why I appreciate the
input from somebody better (ie you!) :)

> while read f; do
>   if /bin/cmp -s "${f}" "/etc/defaults${f}"; then
>     echo $f hasn't been modified, it will be updated     /bin/rm -f
>   "${f}" fi
> done < /etc/preremove/base-files-manifest.lst
> 
> or even
> 
> while read f; do
>   /bin/cmp -s "${f}" "/etc/defaults${f}" && \
>     echo $f hasn't been modified, it will be updated && \     /bin/rm
> -f "${f}" done < /etc/preremove/base-files-manifest.lst
> 
>> but I'll add the test for diffutils :)
> 
> No need -- it should be safe here.  You really need this test if you
> want to distinguish between "false" (i.e., 1..126) and "missing"
> (i.e., 127). 
> 
>> This way the skel files will be upgraded in the same manner.
>> 
>> I have been wondering how best to release this, there have been
>> several patches to profile, but if I release a new package with the
>> new version of profile then the preremove script will never
>> upgrade... but how long do I (we? ;) give people to upgrade?
>> 
>> J.
> 
> Maybe just add a note in the announcement (and, of course, the README)
> that if the /etc/profile doesn't contain any customizations, one
> should remove it before upgrading the "base-files" package to be able
> to get the latest versions in the future...
> 	Igor

OK.  I'll have to create the README - there never has been one!

Give me a few days and I'll post a test version.

J.


This e-mail has come from Experian International: winner of the UK's National Business of the Year Award 2003.

==========================================================================
Information in this e-mail and any attachments are confidential, and may 
not be copied or used by anyone other than the addressee, nor disclosed 
to any third party without our permission. There is no intention to 
create any legally binding contract or other binding commitment through 
the use of this electronic communication unless it is issued in accordance 
with the Experian Limited standard terms and conditions of purchase or 
other express written agreement between Experian Limited and the recipient 
Experian Limited (registration number 653331) Registered office: 
Talbot House, Talbot Street, Nottingham NG80 1TH

Although Experian has taken reasonable steps to ensure that this communication 
and any attachments are free from computer virus, you are advised to take 
your own steps to ensure that they are actually virus free.