From: Luis M. <ga...@ot...> - 2005-02-02 21:46:46
|
Chris Halls wrote: > > >I was thinking of a similar feature, that is not quite as flexible but would >do the same thing but without needing to maintain a config file. > >The idea is to use the Packages files and file databases to decide when to >download new versions. Any packages that had been downloaded by a client >within a certain time (e.g. 2 months, settable by a parameter) could be >automatically updated if a new version appeared in the Packages file for the >backend. If no client requested the package anymore after a certain period, >ap would stop updating that package automatically. > > i think you shoul do that trought the conf file. Defining the time, if it is has a mirror or not. >It's not quite as flexible as your method, but would perhaps be easier from >the user point of view, because there would be only 1 parameter to tweak >instead of having to maintain a list of packages. > > For this case there is no need to have the packages installed. justa make a txt list from dpkg -l > list.txt and the apt-get install `cat list.txt` -d . I use that to have semi-automated esktop instalations and quite popular between the newbies. >But whichever version you prefer, if you have time to implement it please go >ahead and I'd gladly add it. > >Chris > > >------------------------------------------------------- >This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting >Tool for open source databases. Create drag-&-drop reports. Save time >by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. >Download a FREE copy at http://www.intelliview.com/go/osdn_nl >_______________________________________________ >Apt-proxy-users mailing list >Apt...@li... >https://lists.sourceforge.net/lists/listinfo/apt-proxy-users > > > > |