new 'temp' directory in CVS cinstall contains dependency WIP

[Charles Wilson]

Christopher Faylor wrote:

> Ok.  I'm going to clarify and simplify:
> 
> Here is what I'm asking:
> 
> 1) If you are a package maintainer, check your entries in
>    setup.ini for accuracy.  Make any changes that you think
>    are appropriate.  Check them into cvs.  Ignore the "rh"
>    script.


I've added ldesc entries for all of my packages, as well as
updated the sdesc entries to also include the pkg name first. However, 
I'm having difficulty checking it in; cvs is hanging -- but it's not the 
expected W98 hang-after-done behavior.  I'm on W2K, and it's hanging 
before it begins.  I'm too tired to debug this right now, so I've 
attached a patch.

If you don't want to deal with ldesc entries right now, let me know and 
I'll regen the patch without them.


> 2) Try setup.ini with a freshly compiled setup.exe.  If it
>    works fine for you, you're done.  If it doesn't then debugging
>    is appreciated.


Seems to work okay, even with the multiline ldesc entries.  (I even 
compiled a setup.exe that displayed the ldesc entries instead of the 
sdesc ones, and it seemed to work okay -- more than just the first line 
of the ldesc entry was displayed, although the chooser rendered it 
all-as-one-line-with-no-breaks.)


> - I switched to the Debian categories because I thought that was
>   the consensus.
> 


Well, setup doesn't seem to want to display all of the new categories. 
For one thing, it completely ignores "Devel"  and "Net".  I'm not sure 
how the multi-word categories should be treated:

Is Base Shells supposed to be a "Base Shells" category, or does it 
indicate that bash is in both the "Base" category and the "Shells" category?

In either case, the current behavior is: bash is in the "Base" category; 
there is no "Shells" category nor a "Base Shells" category.

--Chuck