Drop year subdirectories to match client structure

Fixes: https://bugs.gentoo.org/show_bug.cgi?id=523828

2 files changed, 70 insertions, 0 deletions

diff --git a/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt b/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt
new file mode 100644
index 0000000..f63ca77
--- /dev/null
+++ b/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt
@@ -0,0 +1,51 @@
+Title: bash-completion-2.1-r90
+Author: Michał Górny <mgorny@gentoo.org>
+Content-Type: text/plain
+Posted: 2014-11-25
+Revision: 1
+News-Item-Format: 1.0
+Display-If-Installed: >=app-shells/bash-completion-2.1-r90
+
+Starting with app-shells/bash-completion-2.1-r90, the framework used to
+enable and manage completions in Gentoo is finally changing in order to
+properly follow upstream design. This has some important implications
+for our users.
+
+Firstly, the install location for completions changes to follow upstream
+default. The completions enabled before the upgrade will continue to
+work but you may no longer be able to enable or disable completions
+installed prior to the upgrade. To solve this issue, the packages
+installing completions need to rebuilt. The following command can be
+used to automatically rebuild all the relevant packages:
+
+$ find /usr/share/bash-completion -maxdepth 1 -type f \
+	'!' -name 'bash_completion' -exec emerge -1v {} +
+
+Secondly, the autoloading support introduced upstream removes the
+penalties involved with enabling a great number of completions. This
+allowed us to switch to an opt-out model where all completions installed
+after the upgrade are enabled by default. Specific completions can be
+disabled using 'eselect bashcomp disable ...'
+
+The model change implies that all current selections done using 'eselect
+bashcomp' can not be properly migrated and will be disregarded when
+the relevant completion files are built against the new bash-completion
+version. After rebuilding all the packages providing completion files,
+you may want to remove the symlinks that were used to configure
+the previous framework using the following command:
+
+$ find /etc/bash_completion.d -type l -delete
+
+Thirdly, we have solved the issue causing bash-completion support to be
+enabled by default on login shells only. If you needed to explicitly
+source 'bash_completion' script in bashrc, you can safely remove that
+code now since system-wide bashrc takes care of loading it.
+
+Lastly, we would like to explain that USE=bash-completion is being
+removed from packages for the completions will be installed
+unconditionally now. However, this will result in some implicit
+dependencies being removed. Most specifically, users wishing to use
+bash-completion will have to request app-shells/bash-completion
+explicitly, e.g.:
+
+$ emerge -n app-shells/bash-completion
diff --git a/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt.asc b/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt.asc
new file mode 100644
index 0000000..ed9cc4f
--- /dev/null
+++ b/2014-11-25-bash-completion-2_1-r90/2014-11-25-bash-completion-2_1-r90.en.txt.asc
@@ -0,0 +1,19 @@
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v2
+
+iQJ8BAABCgBmBQJUc7wdXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
+ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2REJCMDdDQzRGMERBRDA2RUEwQUZFNDFC
+MDdBMUFFQUVGQjQ0NjRFAAoJELB6GurvtEZOVSgQAIr354YAxhE2gRS/fyG0r0WD
+5wipNaYU1tgcNmN1GFhasp2cwLPdmFNueqvp/MUoR/rA9U1yvNhGRDjJS++KF4u7
+nbWSZczWBfxDTGuDJ4+uS3BkeeFGsL2z2v+tkKZUfnnK0c6ZW7Qk9pUZNqRBnptP
+QKjWikq98Dn0+jJUdiK6fG4LjPUL4B1jvKZUSCtm4jCLsYWymF1ffrZprEyYX3i5
+0T0CqN+HAo8TvosYCPedMJR7Hh4BOSrw1gfZchgPh5gcq0I3zO5zat6HkF1y6joF
+50f+p/f5fSf5xqyTui5sVvb8P99XlKDuGy3EJe4Bah/LKdvot8/NdXh2xL+Bj9QU
+l1MFeUrpktKgNbdzPsmg4VbVy7CTkynVw3tSmNMVc85HP6mpAE6eobSDWCtLf6wm
+f4GJZBK+Sk9Vd3NeyI+QOIUWDs2cfn460HOXiocRDEjEzqB5N3LMWLtYO1Vr7EbN
+NOfuAj2A5Rs2+X4yftN3RcJMQK5fWZQHyEQkkowLZLNIt+54xCs5BCrK2GK1zCi/
++3Yp77Low9M4qjXB2bHblW2Edi5XmxdyNrtDymVbH3QLKKA6JgkBVy+jOacCZkp2
+Dg/1c+Rb3qnW4jWkbvNb3UFFnzl3W7VDLL0wttpwgrVTkA/Ivu/Qe3XH/N0iZdfu
+ZNXVGXYhTIySbu18cb7O
+=UzD3
+-----END PGP SIGNATURE-----