Simple Package Manager

[Schachner Thomas]

Hello!

Have you ever wondered why you have not full control over your installed
files.
-> you have a rpm based system an then there is the moment that your
favorite program
is not available as rpm package for your distribution! You are to lazy to
read all the document about generating rpm packages. So you grab the source
code 
make the magic ./configure --with-option bla && make && make install and
then
all your system isn't anymore in your hands because there are installed
serveral files
in several location , eventual over some existing package based file, so
that these
packages are no longer valid.

So my question :

Why isn't there a ./configure && make && make install driven Package Manager
which
sits in the coreutils?

I dont know, but i have hacked the install.c program to provide a sqlite (
simple small c based sql database) based package manager for source code as
long the install part uses the install program.

The goal's are:

1.) Install from everywhere ( source,rmp,deb ..and all formats out there )
2.) Easy extract a package from an existing system so that it can be
transfered and installed simple with one command on another system.
3.) get metadata with for example stat utility on a file ( package_name,
package_version ..)
4.) have a tool which can check easy consistence of package on filesystem (
permissions,owner,group,checksums ) so you can run this tool to identify
changed files for a package, or all of you packages

In the existing version which already works for me, there is a database file
in /etc which
you can choose with the enviroment key REGISTRY in which the table package
lives.
with the sqlite command tool you can query all data in a sql fashioned way,
and can be
easy used in shell scripts. ( actual i can log
package_name,package_version,permission,inode ) planned is to have also
autor,owner,group,hostname,haveacl,filesystem .. what we want.

I also plan to use this sqlite database for an KDE/GNOME package frontend,
where the user can grab any source code and can simple install all flavours
of packages and source ( only if the make install uses the install program )
How are the chances to get this code in, with a configure option ?
And who can help me, because i am a not so good c programmer.

Can anyone tell me if there is a chance to get the configure options from
the generated Makefile to store this information also in the package table?

Bye Thomas