I generally stick with base, versioned, and repository atoms though, as slots are generally not important and wildcards can match unintended things if you're not careful. You can combine these as well, so "<*/python*-9999:3.6::test" would be a valid atom specification. They're not really used in a a dependency sense, but as they are sent to the ebuild system they roughly follow the same rules. Wildcards: arbitrary substitution (e.g.Repository: category/package-version::repository (e.g.Slot: category/package-version:slot (e.g. dev-lang/python-3.4.5), with or without comparison operators Version: category/package-version (e.g.According to its man page, it supports the following atom types: our conceptualization of the atom, which consists of a nucleus surrounded by electrons. Portage's use of atoms is slightly different, however. In fact, the word quantum has Latin roots and means how much. This is what ebuilds use internally and is not really necessary for everyday use, as only package maintainers see these regularly (you will see slots, though.) Atom USE statements: deals with USE flags.dev-lang/python-3.4.5:3.4/3.4m, which can be installed at the same time as :2.7 and :3.6, for example) Atom slots/sub-slots: versions of a package that can co-exist (e.g.Extended atom prefixes/postfixes: wildcards and blockers (e.g.
0 Comments
Leave a Reply. |