Remove phab migration documentation (#379)

The other documentation is sufficiently up to date that the warning can be removed. Rename the `.mdx` pages to `.md` to make GitHub render diffs again.
getsolus · Sep 20, 2023 · dba7afd · dba7afd
1 parent de3cba0
commit dba7afd
Show file tree

Hide file tree

Showing 8 changed files with 5 additions and 124 deletions.
diff --git a/docs/packaging/_markdown-migration-warning.md b/docs/packaging/_markdown-migration-warning.md
diff --git a/docs/packaging/creating-a-new-package.md b/docs/packaging/creating-a-new-package.md
@@ -156,7 +156,6 @@ Once the build completes, your directory should now include the following files:
 ```text
 ├── abi_used_libs
 ├── abi_used_symbols
-├── Makefile
 ├── package.yml
 ├── pspec_x86_64.xml
 └── tree-2.1.1-1-1-x86_64.eopkg

diff --git a/docs/packaging/index.mdx → docs/packaging/index.md b/docs/packaging/index.mdx → docs/packaging/index.md
@@ -4,17 +4,13 @@ summary: Steps for setting up a packaging environment and submitting packages
 sidebar_position: 0
 ---
 
-import MigrationWarning from './_markdown-migration-warning.md';
-
-<MigrationWarning/>
-
 # Packaging Overview
 
 This is the overall workflow for creating or updating a package.
 
 ## Development Environment Preparation
 
-1. [Prepare for Packaging](prepare-for-packaging.mdx)
+1. [Prepare for Packaging](prepare-for-packaging.md)
 2. Review the [requirements for the package.yml file](docs/packaging/package.yml.md).
 3. Also review our [Packaging Practices](docs/packaging/packaging-practices.md).
 

diff --git a/docs/packaging/prepare-for-packaging.mdx → docs/packaging/prepare-for-packaging.md b/docs/packaging/prepare-for-packaging.mdx → docs/packaging/prepare-for-packaging.md
@@ -4,10 +4,6 @@ summary: Quick guide on getting your system set up for packaging on Solus
 sidebar_position: 1
 ---
 
-import MigrationWarning from './_markdown-migration-warning.md';
-
-<MigrationWarning/>
-
 # Prepare for Packaging
 
 ## Switch to the Unstable Repository

diff --git a/docs/packaging/procedures/diff-to-pull-request.md b/docs/packaging/procedures/diff-to-pull-request.md
diff --git a/docs/packaging/procedures/migrate-repos-to-github.md b/docs/packaging/procedures/migrate-repos-to-github.md
diff --git a/docs/packaging/submitting-a-pull-request.md b/docs/packaging/submitting-a-pull-request.md
@@ -19,9 +19,8 @@ At minimum, your pull request will include changes for the following files:
 - `package.yml`
 - `pspec_*.xml`
 
-It will also include these files:
+It may also include these files:
 
-- `Makefile`
 - `MAINTAINERS.md`
 
 Double check the `package.yml` to make sure the builddeps are in the right order, and that it otherwise adheres to the [standards](package.yml.md) Solus has set.

diff --git a/docs/packaging/your-first-package-update.md b/docs/packaging/your-first-package-update.md
@@ -5,7 +5,7 @@ summary: An example of how to build a package that exists in the Solus repos for
 
 # Your First Package Update
 
-This page will guide you through the steps required to build your first package. This is really a test to make sure that your [build environment is set up correctly](docs/packaging/prepare-for-packaging.mdx). You will clone an existing package, build it, then install it, and finally remove it.
+This page will guide you through the steps required to build your first package. This is really a test to make sure that your [build environment is set up correctly](docs/packaging/prepare-for-packaging.md). You will clone an existing package, build it, then install it, and finally remove it.
 
 ## Cloning and building `nano`
 
@@ -58,10 +58,9 @@ You will be prompted to enter your password by sudo, and the `solbuild` tool wil
 If the build is successful, you will have a `nano` package file with a name like `nano-7.2-161-1-x86_64.eopkg`. Run the `ls` tool to check the exact name:
 
 ```bash
-ls
-
+$ ls
 abi_used_libs     files       package.yml
-abi_used_symbols  Makefile  nano-7.2-162-1-x86_64.eopkg  pspec_x86_64.xml
+abi_used_symbols  nano-7.2-162-1-x86_64.eopkg  pspec_x86_64.xml
 ```
 
 Congratulations! You have successfully built your first package on Solus.