commiting empty files to make portage behave. bug #75277

Long story short, the removal of all of these top level 'target' profiles make.defaults == portage screwing up use arch checks in bash.
Remove these once portage a sane portage version has been out long enough that backwards compatability is no longer an issue.

diff --git a/profiles/default-linux/x86/2004.0/make.defaults b/profiles/default-linux/x86/2004.0/make.defaults
new file mode 100644 (file)
index 0000000..e69de29

diff --git a/profiles/default-linux/x86/2004.2/gcc34/2.6/make.defaults b/profiles/default-linux/x86/2004.2/gcc34/2.6/make.defaults
new file mode 100644 (file)
index 0000000..e69de29

diff --git a/profiles/default-linux/x86/2004.2/gcc34/make.defaults b/profiles/default-linux/x86/2004.2/gcc34/make.defaults
new file mode 100644 (file)
index 0000000..e69de29

diff --git a/profiles/default-linux/x86/2004.2/make.defaults b/profiles/default-linux/x86/2004.2/make.defaults
new file mode 100644 (file)
index 0000000..e69de29

diff --git a/profiles/default-linux/x86/2004.3/make.defaults b/profiles/default-linux/x86/2004.3/make.defaults
new file mode 100644 (file)
index 0000000..e69de29

diff --git a/profiles/default-linux/x86/2005.0/make.defaults b/profiles/default-linux/x86/2005.0/make.defaults
new file mode 100644 (file)
index 0000000..e69de29

diff --git a/profiles/default-linux/x86/gcc2/make.defaults b/profiles/default-linux/x86/gcc2/make.defaults
new file mode 100644 (file)
index 0000000..e69de29

diff --git a/profiles/default-linux/x86/gcc31/make.defaults b/profiles/default-linux/x86/gcc31/make.defaults
new file mode 100644 (file)
index 0000000..e69de29