Re: Re: rocket search

> > Yes, sure. I just don't know why you'd stop halfway through. This way
> > you can search a part of the flist, but not all of it. I think that's
> > worse than nothing.
> 
> I don't think so. I usually want to search in the package description, the
> categories or the bins and libs list.
But then we should issue a warning that this feature does not search the
whole flist. Because if someone then searches for an obscure header file
of an exotic library that happens to be packaged a user would get the
impression that the library is not packaged.

>And here is a good argument for not including the rest of the flist too:
> 
> # egrep -r '(bin/|lib/[^/]*\.so$)' /var/adm/flists/ | cut -f2- -d: | wc
>    6324   12648  193977
> 
> # egrep -r '.' /var/adm/flists/ | cut -f2- -d: | wc
>  366627  733320 21482299
Oh, I wouldn't seriously propose doing so :) It's just that I was confused
by the "half" feature.

> the flist is in the packages.db already (implicit, because the file cksums
> are in there). But the packages.db is for binary packages (as I've
> explained already).
And the partial flist is created just before a binary package is created so
they essentially use the same data.
Guess I'll just wait for an implementation because I see only one advantage
of duplicating this information: if the packages.db and a rock-src checkout
are of different dates, which is a bad anything anyway.


Greetings,
	blindy

-- 
Benjamin 'blindCoder' Schieder
Registered Linux User #289529: http://counter.li.org
finger blindcoder-1k+CIuW/[email protected] | gpg --import
-- 
/lusr/bin/brain: received signal: SIGIDIOT

_______________________________________________
rock-devel mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB7ONC7Wabow2Um2YRAohTAJ9O4KcbsQUG2Gm3lTGxmVR4zQLSYwCfSRjR
4XUnUd6JEr3TVDVPQIax0ks=
=y7ol
-----END PGP SIGNATURE-----