I have a pretty good idea for a package manager. I am going to use this on my LFS system--a brand new 1GHz Athlon for college--to keep updated about packages. I am thinking of modifying "make" to check the arguments, see if there is a "make install" somewhere in there. If there is, it will save the name of the current directory into a database, along with a list of all the installed files, hence, we must modify "install". But, it will have a config file somewhere that tells it to watch certain ftp/http sites for updates to packages. it will be much easier to do this with ftp instead of http...but anyway, a gui front end will allow you to tell it what sites to watch, and how often to watch them. So, if I have package x, modified Jan 1, 2001, and I set it up to run once a month, if in Feb, 2001, package x is updated on sourceforge, it will send me an email saying that a new version has been posted at sourceforge, give me the download url, and allow me to view documentation( README, *.txt, INSTALL, FAQ, etc ) according to regexp parsing, or install the package( through some kind of configure/make frontend). this allows me to concentrate on my schoolwork/programming while simultaneously allowing me to update my system. Any other ideas?
Justin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thats a good idea for maintenance, but what about the install process?... you need a package system that can hanlde the system from 0, rpm is not so good, i prefer debian package manager, anyway... you can swithc from one to another and vice.... i think this is a issue regarding the package procces, the "magic make" idea is a good one, i found in feshmeat.net a modified make to do this, we can try but i am not sure how stable is telling our system to download and resintall sendmail in a prod enviroment, or.. what about a kernel upgrade??, how about all the patches we install to the kernel??... yes i know make oldconfig do the trick, but the patches (security elated ones) arre not so standar like the rest.. i prefer looking to the magic make idea for a "running" system in a contolled enviroment and not in a "production" one.... i hate to reinstall my web server or the fiel serve just for a kernel upgrade... you know how is unix... if is uop and running.. let it go... and dont mess with it...
Bye...
Juan Diego
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a pretty good idea for a package manager. I am going to use this on my LFS system--a brand new 1GHz Athlon for college--to keep updated about packages. I am thinking of modifying "make" to check the arguments, see if there is a "make install" somewhere in there. If there is, it will save the name of the current directory into a database, along with a list of all the installed files, hence, we must modify "install". But, it will have a config file somewhere that tells it to watch certain ftp/http sites for updates to packages. it will be much easier to do this with ftp instead of http...but anyway, a gui front end will allow you to tell it what sites to watch, and how often to watch them. So, if I have package x, modified Jan 1, 2001, and I set it up to run once a month, if in Feb, 2001, package x is updated on sourceforge, it will send me an email saying that a new version has been posted at sourceforge, give me the download url, and allow me to view documentation( README, *.txt, INSTALL, FAQ, etc ) according to regexp parsing, or install the package( through some kind of configure/make frontend). this allows me to concentrate on my schoolwork/programming while simultaneously allowing me to update my system. Any other ideas?
Justin
Isn't this something on the lines of the ports system in *BSD ? Can't we use the ports system itself here ?
ing about. But I will look into it to see what it's all about. Thanks for telling me. ( now I'm posting in the right order.....)
Justin
I have never used BSD, so I have no idea what your talking about. But I will look into it to see what it's all about. Thanks for telling me.
Justin
Hi everybody....
thats a good idea for maintenance, but what about the install process?... you need a package system that can hanlde the system from 0, rpm is not so good, i prefer debian package manager, anyway... you can swithc from one to another and vice.... i think this is a issue regarding the package procces, the "magic make" idea is a good one, i found in feshmeat.net a modified make to do this, we can try but i am not sure how stable is telling our system to download and resintall sendmail in a prod enviroment, or.. what about a kernel upgrade??, how about all the patches we install to the kernel??... yes i know make oldconfig do the trick, but the patches (security elated ones) arre not so standar like the rest.. i prefer looking to the magic make idea for a "running" system in a contolled enviroment and not in a "production" one.... i hate to reinstall my web server or the fiel serve just for a kernel upgrade... you know how is unix... if is uop and running.. let it go... and dont mess with it...
Bye...
Juan Diego