https://wiki.archlinux.org/api.php?action=feedcontributions&user=Dunsmoreb&feedformat=atomArchWiki - User contributions [en]2024-03-29T00:57:19ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=User:Dunsmoreb&diff=330851User:Dunsmoreb2014-08-18T03:13:47Z<p>Dunsmoreb: </p>
<hr />
<div>* '''Email''' - mailto:dunsmoreb@gmail.com</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb&diff=281316User:Dunsmoreb2013-11-04T01:28:54Z<p>Dunsmoreb: </p>
<hr />
<div>* '''GitHub''' - https://github.com/dunsmoreb<br />
* '''Email''' - mailto:dunsmoreb@gmail.com<br />
<br />
== Pacman Development ==<br />
<br />
* [[User:dunsmoreb/Pacman_Hooks | Pacman Hooks]]</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb/Pacman_Hooks&diff=259354User:Dunsmoreb/Pacman Hooks2013-05-28T16:49:05Z<p>Dunsmoreb: /* Hooks */</p>
<hr />
<div>This is my proposal/design document for adding hooks to pacman. This is based off of [[User:Allan/Pacman_Hooks | Allan's proposal]].<br />
<br />
== Terminology ==<br />
<br />
The following is a list of terminology used in this document.<br />
<br />
:; Trigger: A trigger is a file where hooks are configured.<br />
:; Hook: A hook is a description of what should be executed whenever a hook type is called.<br />
:; Hook Type: A hook type is an action that different hooks can subscribe to.<br />
<br />
== Goal ==<br />
<br />
The goal of adding hooks to pacman is to allow users and programs to do certain tasks automatically. For example a user could automatically rebuild a package when ever another package is upgraded. Or a program could keep track of all installed/upgraded packages.<br />
<br />
== Trigger Files ==<br />
<br />
Trigger files are similar to [[Systemd | Systemd's]] service files. They are stored in {{ic|/usr/lib/pacman/hooks/triggers}} or {{ic|/etc/pacman.d/hooks/triggers}} and use the same {{ic|.ini}}-style format. By default all triggers are disabled. In order to enable them they should be symlinked to {{ic|/etc/pacman.d/hooks/enabled-triggers}}.<br />
<br />
=== [Trigger] Section ===<br />
<br />
The {{ic|[trigger]}} section is used for describing the trigger itself. It includes two simple fields, ''name'' and ''description''.<br />
<br />
:; Name: The name of the trigger. Used for starting/stopping and enabling/disabling the trigger.<br />
:; Description: The description of the trigger's functionality. Used to inform the user.<br />
<br />
=== [Hook] Section ===<br />
<br />
The {{ic|[hook]}} section allows programs to subscribe to different hook types. There can be multiple hook sections in each trigger file and each type of hook can be repeated more than once.<br />
<br />
:; Hook: The type of hook to listen to. Whenever this hook is called the command specified by {{ic|Exec}} will be ran.<br />
:; Exec: The path to the program to execute. Information about the hook can be passed through arguments in the format {{ic|%x}} where {{ic|x}} is the name of the information to pass.<br />
<br />
== Hooks ==<br />
<br />
Hooks should be provided for every (or almost every) option that pacman provides to the end user. Such as ''install'', ''sync'', ''remove'', etc. When a hook is called the {{ic|Exec}} command is ran with the following variables replaced.<br />
<br />
:; {{ic|%t}}: The hook type. Such as ''install'', ''sync'', ''remove'', etc.<br />
:; {{ic|%p}}: The name of packages passed to pacman.<br />
:; {{ic|%f}}: The flags passed to pacman.</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb/Pacman_Hooks&diff=258837User:Dunsmoreb/Pacman Hooks2013-05-26T03:15:28Z<p>Dunsmoreb: Add terminology section.</p>
<hr />
<div>This is my proposal/design document for adding hooks to pacman. This is based off of [[User:Allan/Pacman_Hooks | Allan's proposal]].<br />
<br />
== Terminology ==<br />
<br />
The following is a list of terminology used in this document.<br />
<br />
:; Trigger: A trigger is a file where hooks are configured.<br />
:; Hook: A hook is a description of what should be executed whenever a hook type is called.<br />
:; Hook Type: A hook type is an action that different hooks can subscribe to.<br />
<br />
== Goal ==<br />
<br />
The goal of adding hooks to pacman is to allow users and programs to do certain tasks automatically. For example a user could automatically rebuild a package when ever another package is upgraded. Or a program could keep track of all installed/upgraded packages.<br />
<br />
== Trigger Files ==<br />
<br />
Trigger files are similar to [[Systemd | Systemd's]] service files. They are stored in {{ic|/usr/lib/pacman/hooks/triggers}} or {{ic|/etc/pacman.d/hooks/triggers}} and use the same {{ic|.ini}}-style format. By default all triggers are disabled. In order to enable them they should be symlinked to {{ic|/etc/pacman.d/hooks/enabled-triggers}}.<br />
<br />
=== [Trigger] Section ===<br />
<br />
The {{ic|[trigger]}} section is used for describing the trigger itself. It includes two simple fields, ''name'' and ''description''.<br />
<br />
:; Name: The name of the trigger. Used for starting/stopping and enabling/disabling the trigger.<br />
:; Description: The description of the trigger's functionality. Used to inform the user.<br />
<br />
=== [Hook] Section ===<br />
<br />
The {{ic|[hook]}} section allows programs to subscribe to different hook types. There can be multiple hook sections in each trigger file and each type of hook can be repeated more than once.<br />
<br />
:; Hook: The type of hook to listen to. Whenever this hook is called the command specified by {{ic|Exec}} will be ran.<br />
:; Exec: The path to the program to execute. Information about the hook can be passed through arguments in the format {{ic|%x}} where {{ic|x}} is the name of the information to pass.<br />
<br />
== Hooks ==<br />
<br />
Hooks should be provided for every (or almost every) option that pacman provides to the end user. Such as ''install'', ''sync'', ''remove'', etc. When a hook is called the {{ic|Exec}} command is ran with the following variables replaced.<br />
<br />
:; {{ic|%t}}: The hook type. Such as ''install', ''sync'', ''remove'', etc.<br />
:; {{ic|%p}}: The name of packages passed to pacman.<br />
:; {{ic|%f}}: The flags passed to pacman.</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb/Pacman_Hooks&diff=258836User:Dunsmoreb/Pacman Hooks2013-05-26T03:11:21Z<p>Dunsmoreb: Added hooks section.</p>
<hr />
<div>This is my proposal/design document for adding hooks to pacman. This is based off of [[User:Allan/Pacman_Hooks | Allan's proposal]].<br />
<br />
== Goal ==<br />
<br />
The goal of adding hooks to pacman is to allow users and programs to do certain tasks automatically. For example a user could automatically rebuild a package when ever another package is upgraded. Or a program could keep track of all installed/upgraded packages.<br />
<br />
== Trigger Files ==<br />
<br />
Trigger files are similar to [[Systemd | Systemd's]] service files. They are stored in {{ic|/usr/lib/pacman/hooks/triggers}} or {{ic|/etc/pacman.d/hooks/triggers}} and use the same {{ic|.ini}}-style format. By default all triggers are disabled. In order to enable them they should be symlinked to {{ic|/etc/pacman.d/hooks/enabled-triggers}}.<br />
<br />
=== [Trigger] Section ===<br />
<br />
The {{ic|[trigger]}} section is used for describing the trigger itself. It includes two simple fields, ''name'' and ''description''.<br />
<br />
:; Name: The name of the trigger. Used for starting/stopping and enabling/disabling the trigger.<br />
:; Description: The description of the trigger's functionality. Used to inform the user.<br />
<br />
=== [Hook] Section ===<br />
<br />
The {{ic|[hook]}} section allows programs to subscribe to different hooks. There can be multiple hook sections in each trigger file and each type of hook can be repeated more than once.<br />
<br />
:; Hook: The type of hook to listen to. Whenever this hook is called the command specified by {{ic|Exec}} will be ran.<br />
:; Exec: The path to the program to execute. Information about the hook can be passed through arguments in the format {{ic|%x}} where {{ic|x}} is the name of the information to pass.<br />
<br />
== Hooks ==<br />
<br />
Hooks should be provided for every (or almost every) option that pacman provides to the end user. Such as ''install'', ''sync'', ''remove'', etc. When a hook is called the {{ic|Exec}} command is ran with the following variables replaced.<br />
<br />
:; {{ic|%t}}: The hook type. Such as ''install', ''sync'', ''remove'', etc.<br />
:; {{ic|%p}}: The name of packages passed to pacman.<br />
:; {{ic|%f}}: The flags passed to pacman.</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb/Pacman_Hooks&diff=258834User:Dunsmoreb/Pacman Hooks2013-05-26T02:53:10Z<p>Dunsmoreb: Added trigger spec files.</p>
<hr />
<div>This is my proposal/design document for adding hooks to pacman. This is based off of [[User:Allan/Pacman_Hooks | Allan's proposal]].<br />
<br />
== Goal ==<br />
<br />
The goal of adding hooks to pacman is to allow users and programs to do certain tasks automatically. For example a user could automatically rebuild a package when ever another package is upgraded. Or a program could keep track of all installed/upgraded packages.<br />
<br />
== Trigger Files ==<br />
<br />
Trigger files are similar to [[Systemd | Systemd's]] service files. They are stored in {{ic|/usr/lib/pacman/hooks/triggers}} or {{ic|/etc/pacman.d/hooks/triggers}} and use the same {{ic|.ini}}-style format. By default all triggers are disabled. In order to enable them they should be symlinked to {{ic|/etc/pacman.d/hooks/enabled-triggers}}.<br />
<br />
=== [Trigger] Section ===<br />
<br />
The {{ic|[trigger]}} section is used for describing the trigger itself. It includes two simple fields, ''name'' and ''description''.<br />
<br />
:; Name: The name of the trigger. Used for starting/stopping and enabling/disabling the trigger.<br />
:; Description: The description of the trigger's functionality. Used to inform the user.<br />
<br />
=== [Hook] Section ===<br />
<br />
The {{ic|[hook]}} section allows programs to subscribe to different hooks. There can be multiple hook sections in each trigger file and each type of hook can be repeated more than once.<br />
<br />
:; Hook: The type of hook to listen to. Whenever this hook is called the command specified by {{ic|Exec}} will be ran.<br />
:; Exec: The path to the program to execute. Information about the hook can be passed through arguments in the format {{ic|%x}} where {{ic|x}} is the name of the information to pass.</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb/Pacman_Hooks&diff=258833User:Dunsmoreb/Pacman Hooks2013-05-26T02:44:38Z<p>Dunsmoreb: Created page with "This is my proposal/design document for adding hooks to pacman. This is based off of Allan's proposal. == Goal == The goal of adding hooks to p..."</p>
<hr />
<div>This is my proposal/design document for adding hooks to pacman. This is based off of [[User:Allan/Pacman_Hooks | Allan's proposal]].<br />
<br />
== Goal ==<br />
<br />
The goal of adding hooks to pacman is to allow users and programs to do certain tasks automatically. For example a user could automatically rebuild a package when ever another package is upgraded. Or a program could keep track of all installed/upgraded packages.<br />
<br />
== Trigger Files ==<br />
<br />
Trigger files are similar to [[Systemd | Systemd's]] service files. They are stored in {{ic|/usr/lib/pacman/hooks/triggers}} or {{ic|/etc/pacman.d/hooks/triggers}} and use the same {{ic|.ini}}-style format. By default all triggers are disabled. In order to enable them they should be symlinked to {{ic|/etc/pacman.d/hooks/enabled-triggers}}.<br />
<br />
=== [Trigger] Section ===</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb&diff=258832User:Dunsmoreb2013-05-26T02:22:22Z<p>Dunsmoreb: Proper link pacman hooks.</p>
<hr />
<div>I'm a programmer who likes to read and learn.<br />
<br />
* '''GitHub''' - https://github.com/dunsmoreb<br />
* '''Email''' - mailto:dunsmoreb@gmail.com<br />
<br />
== Favorite Books ==<br />
<br />
* ''The Inheritance Cycle'' by Christopher Paolini<br />
* ''A Series of Unfortunate Events'' by Daniel Handler<br />
* ''Exodus'' by Leon Uris<br />
* ''Mila 18'' by Leon Uris<br />
<br />
== Pacman Development ==<br />
<br />
* [[User:dunsmoreb/Pacman_Hooks | Pacman Hooks]]</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb&diff=258831User:Dunsmoreb2013-05-26T02:21:28Z<p>Dunsmoreb: Add pacman development section.</p>
<hr />
<div>I'm a programmer who likes to read and learn.<br />
<br />
* '''GitHub''' - https://github.com/dunsmoreb<br />
* '''Email''' - mailto:dunsmoreb@gmail.com<br />
<br />
== Favorite Books ==<br />
<br />
* ''The Inheritance Cycle'' by Christopher Paolini<br />
* ''A Series of Unfortunate Events'' by Daniel Handler<br />
* ''Exodus'' by Leon Uris<br />
* ''Mila 18'' by Leon Uris<br />
<br />
== Pacman Development ==<br />
<br />
* [[Pacman Hooks]]</div>Dunsmorebhttps://wiki.archlinux.org/index.php?title=User:Dunsmoreb&diff=258830User:Dunsmoreb2013-05-26T02:19:54Z<p>Dunsmoreb: Created page with "I'm a programmer who likes to read and learn. * '''GitHub''' - https://github.com/dunsmoreb * '''Email''' - mailto:dunsmoreb@gmail.com == Favorite Books == * ''The Inherita..."</p>
<hr />
<div>I'm a programmer who likes to read and learn.<br />
<br />
* '''GitHub''' - https://github.com/dunsmoreb<br />
* '''Email''' - mailto:dunsmoreb@gmail.com<br />
<br />
== Favorite Books ==<br />
<br />
* ''The Inheritance Cycle'' by Christopher Paolini<br />
* ''A Series of Unfortunate Events'' by Daniel Handler<br />
* ''Exodus'' by Leon Uris<br />
* ''Mila 18'' by Leon Uris</div>Dunsmoreb