[Cuis] Cuis-Features

[Juan Vuletich]

Hi Ken,

This is just great. I want to integrate it into Cuis, and make packages 
know about this.

Something that is not clear to me, is if a package might implement more 
than one feature. I'd think yes, but then FeatureSpec 'provides' needs 
to be a collection. In addition, we have several version.revision number 
in a package, one for each feature it provides. This also means that we 
might need a version.revision for the package too. But I don't want to 
make it more complicated than needed. Thoughts?

BTW, the requirements should be specified as featureName + version, 
without including revision number. Do you agree?

I might have a few hours this Saturday for this. It would be cool to 
agree on these details, so I can proceed. If anyone wants to talk, I'm 
jvuletich at Skype. I'm not always online, and usually can't talk during 
work hours, but feel free to connect and text chat anytime.

Cheers,
Juan Vuletich

On 6/30/2013 6:58 PM, KenD wrote:
> Actually, I went the other way. I'll do a "git push" presently.
> I must to admit that I was in a hurry in the first pass and "did not have the time to make it shorter".
>
>
> I simplified to 2 classes: FeatureSpec and Feature.
>
> One now writes:
>     (Feature named: #Sound version: 1 revision: 0) require.
>
> The rationale is that the data structure is for inclusion in packages and one really wants a user to specify version and revision, so I removed the short form.
>
> All feedback welcomed!
>