Re: new to current-server

On Fri, 2001-12-07 at 05:49, [email protected] wrote:
> Hi, 
> I'm started testing current server for use in my
> systems and I have some comments (I don't know
> python to make the changes) :
> 
> I make a mirror of redhat ftp server to get the
> updates. Sometimes redhat remain with the
> versions of same package, can be possible to
> make current ignore the old versions instead of
> stoping. Maybe an configurable option.

This will be added to the TODO, but after 1.0. 

Here's why: when current notices the conflict, its already added
the old version to the database. The code would either need a delete
(not too hard, but not trivial either) or add another pass doing version
checking. 

Since the plan is to allow package deletes anyway at some point, 
option 1 is what will be coded. Just not before 1.0

> -----------------
> When creating the database before reading a
> directory for packages check if the directory
> exists, if not show an warning currently it
> stops.

This is where you've specified a directory of rpms and that directory 
doesn't exist? Ok, I can check for that. in create() probably...

> -----------------
> When creating the database check if the
> cirectory exists, if not create, currenty it
> crashes.

Known, it was intentional. I can chanage that if people want.

> -----------------
> When reading package headers if any problem
> occurs show an warning and continue, currently
> it crashes.
> 
> ----------------------
> Using redhat 7.x and above instead of making
> steps in encryption.txt you can do
> cd /usr/share/ssl/certs
> make
> answer the questions and the certificates are
> ready
> 
> and when calling stunnel does not specify the
> certificate it will get the default certificate
> from this directory.

But this won't generate the RHNS-CA-CERTS file that you need, will it?


> -----------------------
> 
> I can help making the spec file for making an
> rpm for current.
> If the people define the directory structure and
> the defaults things to be done I can make the
> spec file. I have already made the xinetd file
> ro call stunnel.

Please send me this xinetd file. The next snapshot will include a
working Makefile for you to build your spec file with.

> 
> At this moment I haven't tested the software
> running, I'm only checking the installation
> part.

Thank you for testing current - obviously, it needs it.

-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.