| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Package-Manager: portage-2.2.26
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.26
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
|
|
| |
Gentoo-Bug: 577274
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.26
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
| |
Bug: 575810
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
| |
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
|
| |
Update to 0.12.6 where upstream included our test patch and regenerated
autotools files.
|
| |
|
|
|
|
| |
Package-Manager: portage-2.2.26
|
|
|
|
| |
Package-Manager: portage-2.2.26
|
| |
|
|
|
|
|
| |
Bump to 0.12.5 that has a few bugfixes, gcc5 build fix most notably
(#546642).
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We've long been exporting the LS_COLORS variable to the default env,
but in practice, there's no reason to be doing this in the majority
of cases. The value we most often load is equivalent to the default
which means we're polluting the env and adding overhead for no gain.
Add a little more code (and one extra `dircolors` exec unfortunately)
to check to see if the LS_COLORS value we found is the default. If
so, don't bother exporting it anymore.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Starting with coreutils-8.24, the dircolors TERM entries are run through
fnmatch rather than being a plain text string. This means our parsing
logic no longer works because we assumed fixed strings. It isn't easy to
process a list of path globs in bash, so rework the code to always run
the dircolors tool. We were doing this anyways in the majority of cases,
so it's not like we're adding that much overhead. The only people who
are negatively impacted are interactive colorless terminals.
Reported-by: Bernd Feige <Bernd.Feige@gmx.net>
|
|
|
|
|
|
|
|
| |
The output of dircolors generally shouldn't be problematic even when it's
unquoted (as it tends to be a long dense string w/out whitespace), but add
quotes anyways just to be safe.
Reported-by: konsolebox@gmail.com
|
|
|
|
|
| |
A bunch of terms end in values like "-256color" and "-color" to indicate
the variant that supports color. Match all of those in the fallback case.
|
|
|
|
|
|
| |
We provide rudimentary TERM checking for BSD which doesn't have dircolors,
but this logic works just as well for all systems such as embedded. Make
this code run whenever dircolors does not exist.
|
|
|
|
|
| |
We've got two cases that check TERM with many common entries,
so make the leading parts look the same.
|
|
|
|
|
|
| |
Gentoo-Bug: 563320
Package-Manager: portage-2.2.27
|
|\
| |
| |
| | |
Pull request: https://github.com/gentoo/gentoo/pull/731
|
| |
| |
| |
| | |
Package-Manager: portage-2.2.27
|
| |
| |
| |
| |
| |
| |
| | |
The patch was added for 2.1-r94 in fab2a7c5536a218bd909b2c7265e9c69296316dc but not for the most recent version
Package-Manager: portage-2.2.27
RepoMan-Options: --force
|
| | |
|
| | |
|
| |
| |
| |
| | |
This makes the history easier to track.
|
| |
| |
| |
| | |
troublesome with the constant disk load (failing drives, flaky network e.g. NFS, etc...). See #517342 for details.
|
| |
| |
| |
| | |
michael@smith-li.com. Add history -a to PROMPT_COMMAND #517342 by Paweł Hajdan, Jr.. Add fix from upstream for variable declare weirdness.
|
| |
| |
| |
| | |
bashrc by default #468094
|
|/ |
|
| |
|
|
|
|
|
| |
Replace all uses of herd with appropriate project maintainers, or no
maintainers in case of herds requested to be disbanded.
|
|
|
|
|
|
| |
GLEP 67 removes the explicit notion of maintainer-needed@g.o being used
for packages lacking maintainers, in favor of assuming maintainer-needed
whenever the package has no maintainers.
|