Immutable flag and packages

[Bear Giles <bear@coyotesong.com>]

Here are some ideas for possible incorporation into 2.1 (or 
later, for some features):

1. "installation" should set the immutable flag for any
   binary files and possiibly some configuration files.
   Likewise, removing or updating a package will need to 
   clear that flag.

   Obviously, this requires a FS with an immutable flag.
   Since most Linux systems use ext2, this shouldn't be
   a problem.  Meanwhile it would make it much harder
   for accidential corruption of the core files.

   Target: 2.1?  

2. On a file system that supports more generalized
   metadata fields (ACL lists are a very limnited
   example), te package manager could attach a lot
   of useful information for interested programs.

   One simple example is the copyright status.  A
   copyleft message, for instance, could include a
   URL which contains a pointer to the associated
   source code.

   Another example would be a "remove utility"
   entry which would allow an improved "rm" utility
   (or perhaps anything that calls "unlink()") to 
   learn the "prefered" way to remove a file.
   For instance, the metadata may contain

     /usr/bin/gcc:
     { remove-utility "dpkg -r gcc_2.7.2.1-1" }

   and presents to the user as

     $ rm /usr/bin/gcc
     Remove gcc_2.7.2.1-1 package [Y/n]?

   Yet another example would be a field that
   supports automatic (background) updates.

   Target: ??? (requires file system metadata)

Bear Giles
bear@coyotesong.com


--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org