>[EMAIL PROTECTED] writes:
> the tree info would be nice but then the list command would get bulky and
> we are already running out of room for short descs and pkg names.
I'm not necessarily asking for a tree view (all though that would be nice maybe
as a verbose option?), but I agree that could get bulky. Maybe just add some
more codes like 'u' for only unstable available and 'u-s' for the fact that
there are stable and unstable versions available.
> If it's in unstable trust me you need to compile from scratch.
I'm completely aware of that fact. However here's the current problem, what
about this:
bitchx 1.0c18-3 IRC client
tells me that it's currently only available as unstable?
> [EMAIL PROTECTED] writes:
>> When going to the website I see that the package is only in the current
>> unstable. I would like that to be differentiated somehow in the listing.
>>
>> And while were at it, how about a way to show if the binary is available
>> so
>> that we know we don't have to compile from scratch.
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
