Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/app-shells/bash/files
Commit message (Collapse)AuthorAgeFilesLines
* app-shells/bash: Revbump to fix bug #597006Lars Wendler2016-10-131-0/+26
| | | | | Package-Manager: portage-2.3.2 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>
* app-shells/bash: Removed rc version.Lars Wendler2016-10-071-36/+0
| | | | | Package-Manager: portage-2.3.1 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>
* app-shells/bash: Revbump to fix CVE-2016-0634 (bug #594496).Lars Wendler2016-09-201-0/+118
| | | | | Package-Manager: portage-2.3.1 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org>
* app-shells/bash: version bump to 4.4_beta2Mike Frysinger2016-08-111-0/+36
|
* app-shells/bash: remove unused patchMichael Mair-Keimberger (asterix)2016-07-161-26/+0
| | | | | | Closes: https://github.com/gentoo/gentoo/pull/1887 Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
* app-shells/bash: bashrc: back out clearing of default LS_COLORS #583814Mike Frysinger2016-06-231-23/+9
| | | | | | | | | The behavior of ls in the default case (when LS_COLORS isn't set) isn't documented well. The manual leads you to believe the defaults will be used when in reality they are not. A scan of the source shows this. So back out some the attempts to optimize the env and go back to exporting LS_COLORS all the time. We'll just have to live with incompat warnings when coreutils upgrades & changes behavior.
* app-shells/bash: version bump to 4.3_p46Mike Frysinger2016-06-231-0/+10
|
* app-shells/bash: bashrc: clean up ls_colors var too #572582Mike Frysinger2016-06-231-0/+1
|
* app-shells/bash: bashrc: avoid always exporting default LS_COLORSMike Frysinger2016-02-031-1/+25
| | | | | | | | | | 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.
* app-shells/bash: bashrc: drop custom parsing of dircolors databases #572582Mike Frysinger2016-02-031-19/+11
| | | | | | | | | | | | 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>
* app-shells/bash: bashrc: quote the output of dircolors #572582#8Mike Frysinger2016-02-031-2/+2
| | | | | | | | 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
* app-shells/bash: bashrc: enable colors for all TERMS that end in "color"Mike Frysinger2016-02-031-1/+1
| | | | | 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.
* app-shells/bash: bashrc: enable fallback TERM color checking for everyoneMike Frysinger2016-02-031-7/+9
| | | | | | 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.
* app-shells/bash: bashrc: simplify/unify TERM checking slightlyMike Frysinger2016-02-031-2/+2
| | | | | We've got two cases that check TERM with many common entries, so make the leading parts look the same.
* app-shells/bash: merge bashrc-r# files back to bashrcMike Frysinger2016-01-262-200/+0
| | | | This makes the history easier to track.
* app-shells/bash: Back out the `history -a` by default as it can be a bit ↵Mike Frysinger2016-01-261-1/+4
| | | | troublesome with the constant disk load (failing drives, flaky network e.g. NFS, etc...). See #517342 for details.
* app-shells/bashrc: Do window title setup through PS1 #223641 by ↵Mike Frysinger2016-01-261-7/+20
| | | | michael@smith-li.com. Add history -a to PROMPT_COMMAND #517342 by Paweł Hajdan, Jr.. Add fix from upstream for variable declare weirdness.
* app-shells/bash: introduce support for bashrc.d directory that is sourced in ↵Michał Górny2016-01-261-1/+5
| | | | bashrc by default #468094
* app-shells/bash: drop old versionsMike Frysinger2016-01-262-90/+0
|
* app-shells/bash: do not leave exit value non-zero in default profile scriptMike Frysinger2015-12-021-1/+3
| | | | | If the .bashrc file does not exist, then the one line check in the profile script leaves $? set to 1. Use a full if statement to avoid that.
* app-shells/bash: backport /dev/fd fix to older versions #431850Mike Frysinger2015-10-202-0/+62
|
* app-shells/bash: version bump to 4.4_betaMike Frysinger2015-10-151-16/+0
|
* proj/gentoo: Initial commitRobin H. Johnson2015-08-0866-0/+3520
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed