processed), but before it is run. The post-hooks are run after the command
itself. Both types of hooks receive an instance of the command object.
-See also global setup hooks in :ref:`packaging-setupcfg`.
+See also global setup hooks in :ref:`setupcfg-spec`.
Sample usage of hooks
.. highlightlang:: cfg
-.. _packaging-setupcfg:
+.. _setupcfg-spec:
*******************************************
Specification of the :file:`setup.cfg` file
**destination**. In the previous example, **doc/doc.man** will be placed in
**destination_doc/doc/doc.man** and **scripts/foo.sh** will be placed in
**destination_scripts/scripts/foo.sh**. (If you want more control on the final
-path, take a look at base_prefix_).
+path, take a look at :ref:`setupcfg-resources-base-prefix`).
The **destination** part of resources declaration are paths with categories.
Indeed, it's generally a bad idea to give absolute path as it will be cross
More control on destination part
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-.. _base_prefix:
+.. _setupcfg-resources-base-prefix:
Defining a base prefix
""""""""""""""""""""""