foodogsquared/wiki
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/wiki.git synced 2025-01-31 10:58:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
ce9c76ca4d
wiki/notebook/2020-09-19-08-31-48.org

34 lines
2.8 KiB
Org Mode
Raw Normal View History

Migrate notes to org-roam v2
2021-05-04 16:07:40 +00:00
:PROPERTIES:
:ID: bfed6daf-4c2b-4426-bab9-2804caa5e079
:END:
Update the files for convention Apparently, the convention (at least starting from 2018) is to make the keywords and block names to be in lowercase as stated from one of the following discussions at https://orgmode.org/list/87tuuw3n15.fsf@nicolasgoaziou.fr/. The files was updated with a one liner of shell. However, this is Emacs and org-mode does have an API to let you do stuff in your config and interact with the documents internally so it is not an elegant solution in any way.
2021-04-01 16:08:15 +00:00
#+title: Functional package management
#+date: "2020-09-19 08:31:48 +08:00"
Update notebook as of 2021-10-09 Welp, I rarely take notes nowadays due to more specialized work and stuff. Though, I should have more incentives for writing. In other words, I'm just lazy. ;p More free-thinking morning sessions should be done soon.
2021-10-09 10:14:46 +00:00
#+date_modified: "2021-09-08 02:42:50 +08:00"
Update the files for convention Apparently, the convention (at least starting from 2018) is to make the keywords and block names to be in lowercase as stated from one of the following discussions at https://orgmode.org/list/87tuuw3n15.fsf@nicolasgoaziou.fr/. The files was updated with a one liner of shell. However, this is Emacs and org-mode does have an API to let you do stuff in your config and interact with the documents internally so it is not an elegant solution in any way.
2021-04-01 16:08:15 +00:00
#+language: en
Add a bunch of notes Well, I forgot to add them into the VCS. Whoops... On the other hand, I'm also trying to make it suitable both for org-roam and neuron at the same time.
2020-09-06 12:43:51 +00:00
Fix formatting and consistency of various notes
2021-07-17 10:24:21 +00:00
Functional package management (FPM) is the next step forward [[https://edolstra.github.io/pubs/nixos-icfp2008-final.pdf][pioneered by Eelco Dolstra]] with [[id:3b3fdcbf-eb40-4c89-81f3-9d937a0be53c][Nix package manager]] as the living implementation. [fn:: Eventually, it became the inspiration for other projects that focuses on reproducibility and security such as [[https://guix.gnu.org/][GNU Guix]] and [[https://silverblue.fedoraproject.org/][Fedora Silverblue]].]
Add a bunch of notes Well, I forgot to add them into the VCS. Whoops... On the other hand, I'm also trying to make it suitable both for org-roam and neuron at the same time.
2020-09-06 12:43:51 +00:00
Update notebook as of 2021-10-09 Welp, I rarely take notes nowadays due to more specialized work and stuff. Though, I should have more incentives for writing. In other words, I'm just lazy. ;p More free-thinking morning sessions should be done soon.
2021-10-09 10:14:46 +00:00
It was first realized from the thesis "[[id:f2e1e2f3-cc34-4c76-91d4-2706ce7756d2][The Purely Functional Software Deployment Model]]".
Migrate notes to org-roam v2
2021-05-04 16:07:40 +00:00
The conceptual overview of it is similar to [[id:7e1e2bcc-6f70-4624-a049-b42f9db5e28b][Functional programming]] with how it views with data and functions (in this case, packages and build processes).
Add a bunch of notes Well, I forgot to add them into the VCS. Whoops... On the other hand, I'm also trying to make it suitable both for org-roam and neuron at the same time.
2020-09-06 12:43:51 +00:00
It views that packages are a unique result from combining different things: dependencies, build processes, versions, and more.
If a dependency has updated its patch version or a build instruction has revised with one line of change, it will result in a "new" package as the output even if the package isn't any different.
Migrate notes to org-roam v2
2021-05-04 16:07:40 +00:00
Coming from a functional approach, it also features statelessness and immutability, making it a reliable toolkit for [[https://reproducible-builds.org/][reproducible builds]] (thus gaining a reach for [[id:6eeb7a24-b662-46d6-9ece-00a5028ff4d8][Reproducible research]]).
Add a bunch of notes Well, I forgot to add them into the VCS. Whoops... On the other hand, I'm also trying to make it suitable both for org-roam and neuron at the same time.
2020-09-06 12:43:51 +00:00
The problems that FPM attempts to solve come from the critique of the traditional package management which is still dominant as of today (2020-08-31).
Here are some of the problems on a traditional Linux-based system:
- The statefulness of the entire system leads to similar situations on Windows' dependency hell problem.
Fix formatting and consistency of various notes
2021-07-17 10:24:21 +00:00
- As a consequence of the statefulness, traceability is almost non-existent.
Add a bunch of notes Well, I forgot to add them into the VCS. Whoops... On the other hand, I'm also trying to make it suitable both for org-roam and neuron at the same time.
2020-09-06 12:43:51 +00:00
- Multiple versions of packages are hard to place side-by-side which is used by developers targetting stable versions while experimenting with the latest versions.
- Destructive ongoing updates which consists of replacing the current version with the updated version while the update is going.
The functional approach with the unique output and immutable variables addresses the listed problems in some way.
- A package is built from an input resulting in a package on a unique immutable location, eliminating the statefulness in the process.
- Since each revision results in a new location, the same package with different versions can be easily placed side-by-side.
- With the way how packages built, the old system can be kept giving the possibility for the user to rollback to those previous versions.
- The functional approach creates a guaranteed output, making it predictable (and traceable).
Reference in New Issue Copy Permalink