On Mon, Aug 31, 2009 at 5:41 PM, Brock Pytlik<[email protected]> wrote:
> Mike Gerdts wrote:
>>
>> On Mon, Aug 31, 2009 at 3:59 PM, Brock Pytlik<[email protected]> wrote:
>>
>>>
>>> David Powell wrote:
>>>
>>>>
>>>> Brock Pytlik wrote:
>>>>
>>>>>
>>>>> I didn't look specifically at SQLite3, at least not that I remember.
>>>>> Revamping search, as I understand it, is low on our priorities, meaning
>>>>> I'm
>>>>> not going to be making any major changes before the next release (and
>>>>> quite
>>>>> possibly after the next release, we've still got a lot of features
>>>>> required). Our impression is that local search is a rare operation
>>>>> since
>>>>> usually, an end user is searching for software they don't already have.
>>>>>
>>>>
>>>>  I find that assessment a little strange, since ultimately people
>>>>  aren't using computers to install software, they are using computers
>>>>  to use software.  Once the software they need is installed searches
>>>>  will primarily be local searches.  To state it differently, remote
>>>>  searches represent a fixed cost, whereas local searches represent an
>>>>  ongoing cost.
>>>>
>>>>  I agree remote searches are very important -- possibly more important
>>>>  than local searches -- but that doesn't mean local searches are rare
>>>>  or negligible.
>>>>
>>>>  Dave
>>>>
>>>>
>>>
>>> Help me understand the use case for frequent local search that I'm not
>>> seeing... Once the software is installed on your machine, why are you
>>> searching for it? I can see doing this once in a great while because the
>>> binary didn't get delivered into a directory that's in your path, and so
>>> you
>>> have to figure out where the silly thing actually got placed. Since I've
>>> been running OpenSolaris, I think I've done that a handful of times.
>>> Other
>>> than that, I can't think of use cases for most of our users.
>>>
>>
>> The most common scenarios for me are:
>>
>> - I'm looking to see if a header file or library exists on the system,
>> but tucked away somewhere other than where the compiler/linker is
>> looking for it.
>> - I just saw a report of a gaping hole in version x.y.z of the blurb
>> executable.  I want to find out if it is installed and if so what
>> version.
>>
>
> Thanks, these two both makes sense to me. Search wouldn't be where I would
> necessarily go to find the version of a program, but I'm glad that works.
>>
>> - I see a problem with an executable or library and want to see if
>> there are any patches to the package (updated package in the new
>> paradigm)
>>
>>
>
> I assume here you're using search to go from library/executable -> package
> to then allow you to check and see if updates are available?

Exactly.

>
> Thanks,
> Brock
>
>



-- 
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to