Packaging: Split pages to reduce duplication and new recipe creation page#72
Packaging: Split pages to reduce duplication and new recipe creation page#72NomadicCore merged 3 commits intomainfrom
Conversation
CookieSource created a draft page for creating a new recipe. Uploading as a draft so we can colaboratively refine To-Do: - Check structure and language against "Updating an existing package recipe" - Answer comments and questions raised - Remove drafting notes
Updated the complete packaging workflow with the addition of a new "Creating a new package recipe" page and then splitting out additional copy into separate pages so copy isn't duplicated across Creating and Updating package recipe pages - New "Preparing for packaging" page - New "Creating a new package recipe" page - New "Building and testing packages" page - New "Checking for package updates" page - Updated "Updating a package recipe" page **Testing** - Built dotdev locally and ensured site was wroking, particularly given the new pages added
|
Hey all, I've worked on this based on @CookieSource previous efforts. I have reworked most of the packaging workflow to separate out additional pages where steps are repeated between "Creating a new package recipe" and "Updating an existing package recipe". One thing I note is using builddeps : as a requirement. @CookieSource didn't catch this in her reproduction so I'm wondering if I could get guidance on how / where we would identify this? I ask as I built the package without that binary as part of this package creation process and it built and worked fine as far as I could see so I don't think a user would pick this up? |
|
So I think the detailed guide already shows someone to go to the website of the creator of a package and reading that documentation simply is always going to be a requirement over any automatic creation. I would say this helps as a starting point so you have a template you can modify based on upstream documentation and dependencies/optional dependencies it's nothing more than that in my eyes. |
NomadicCore
changed the title
|
Looks good to me.! |
2 participants
CookieSource created a draft page for creating a new recipe. Uploading as a draft so we can collaboratively refine
To-Do: