{"id":355,"date":"2025-12-26T14:35:13","date_gmt":"2025-12-26T03:35:13","guid":{"rendered":"https:\/\/securelang.net\/cms\/?p=355"},"modified":"2025-12-26T14:44:35","modified_gmt":"2025-12-26T03:44:35","slug":"1-x-packaging-structure","status":"publish","type":"post","link":"https:\/\/securelang.net\/cms\/blog\/2025\/12\/26\/1-x-packaging-structure\/","title":{"rendered":"1.x Packaging Structure"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Worst Case<\/h2>\n\n\n\n<p>Bunch of files thrown into <em>BOOT:\/<\/em> or <em>RD0:\/<\/em> with minimal documentation (current scenario as of 1.0.1).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Best Case<\/h2>\n\n\n\n<p>Every component neatly packaged and easy to enable, disable or switch out in a particular system build.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Likely Compromise<\/h2>\n\n\n\n<p>System programs will go in the drive&#8217;s <em>\/DOS <\/em>directory and development tools will go in a <em>\/SDK<\/em> directory, maybe with other top-levels for other optional stuff. This will be managed by simply extending mkfs to build &#8220;release packaged&#8221; disk images, the regular package manager will be included in <em>\/DOS<\/em> but not overly relied on by the system itself.<\/p>\n\n\n\n<p>This works in well with the <em>PATH<\/em> system allowing users to look up programs from the current drive or from their <em>BOOT:<\/em> or equivalent drive. E.g. a possible <em>PATH<\/em> setting would be &#8220;\/DOS;BOOT:\/DOS&#8221; allowing lookup of system programs from the current drive&#8217;s installation first when available or otherwise from the <em>BOOT:<\/em> drive. A fully packaged approach may need a more complicated <em>PATH<\/em> instead.<\/p>\n\n\n\n<p>This also allows for easy packaging in the future as any new large components can easily be broken off into subdirectories first and then packaged separately whenever it makes sense.<\/p>\n\n\n\n<p>So that will probably be the compromise used for later 1.x releases rather than the full packaging approach or the &#8220;just chuck the files in&#8221; approach.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Worst Case Bunch of files thrown into BOOT:\/ or RD0:\/ with minimal documentation (current scenario as of 1.0.1). Best Case Every component neatly packaged and easy to enable, disable or switch out in a particular system build. Likely Compromise System programs will go in the drive&#8217;s \/DOS directory and development tools will go in a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"pagelayer_contact_templates":[],"_pagelayer_content":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-355","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/posts\/355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/comments?post=355"}],"version-history":[{"count":4,"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/posts\/355\/revisions"}],"predecessor-version":[{"id":359,"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/posts\/355\/revisions\/359"}],"wp:attachment":[{"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/media?parent=355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/categories?post=355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/securelang.net\/cms\/wp-json\/wp\/v2\/tags?post=355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}