[Octave-bug-tracker] [bug #45369] pkg build leads to duplication of PKG_ADD and PKG_DEL files

[Julien Bect]

Follow-up Comment #8, bug #45369 (project octave):

I propose something else.

1) No longer accept PKG_ADD/PKG_DEL files at the root of the package tarball.

2) Accept PKG_ADD/PKG_DEL files in ./inst, or in any subdirectory of ./inst.
Those files are copied at the corresponding location in the *arch-independent*
directory.

3) Also, accept PKG_ADD/PKG_DEL files in ./src (for source packages) or in
./inst/ARCH-NAME (for binary packages). Those files are copied in the
*arch-dependent* directory.

4) Keep accepting PKG_ADD/PKG_DEL directives as well.

5) When building a binary package, copy PKG_ADD/PKG_DEL directives into
PKG_ADD/PKG_DEL files (this is what we already do) but leave the resulting
files where they are (in particular, do not move them at the root of the
tarball)

6) When installing a binary package, do not copy PKG_ADD/PKG_DEL directives
into PKG_ADD/PKG_DEL files a second time (once is enough !)

7) To make things perfectly clear for package developpers, specify in which
order the two directories (on platforms where they are separate) are loaded
and unloaded, and therefore in which order the corresponding PKG_ADD/PKG_DEL
files are executed.

8) On platforms where the two directories are not separated (does this exist
?), merge the PKG_ADD/PKG_DEL files, when both exist, in the same order as
specified in 7).

How does that sound ?


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45369>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/