I think the name and the attribute name could be named with better
names, to prevent confusion. Perhaps a "label" and "path"/"fully
qualified path". The name is just really used for fuzzy search which I
believe is there for convenience for the operator. Like the difference
between a search engine term, and the actual domain name. If the number
of packages (and package versions) keeps growing, full indexing will be
needed to maintain performance in fuzzy operations.
On 2/09/2014 6:47 AM, Wout Mertens wrote:
Don't forget the nix-env -u case which updates based on name (in fact,
that kinda sucks for sub-attributes like python packages, there are
lots of attributes mapping to the same names).
Wout.
On Mon, Sep 1, 2014 at 10:44 PM, Florent Becker
<florent.bec...@ens-lyon.org <mailto:florent.bec...@ens-lyon.org>> wrote:
On 01/09/2014 11:22, Vladimír C(unát wrote:
> I suggest we distribute the database with the channel, similarly
> to the command-not-found database.
Can't command-not-found suggest using nix-env -iA rather than nix-env
-i? That would be one indirection less for that use case, and
teach new
users about nix-env -iA.
--
Florent
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl <mailto:nix-dev@lists.science.uu.nl>
http://lists.science.uu.nl/mailman/listinfo/nix-dev
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
