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

[Julien Bect]

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

> I think disallowing PKG_ at package root is not the right solution.
>
> Suggestion: PKG_ at package root always only into one directory, either
arch-dependent or -independent. PKG_ directives from source-files or installed
files also each directive only in one of arch-dep. or -indep. directory.
Doesn't actually matter into which. And then: All PKG_ADD directives of a
package should be called only after having added both arch-dep. and -indep.
directory to the path, and correspondingly for PKG_DEL.

If the explanation in my previous post is ok, then this won't really solve the
problem.

What needs to be done, I think, is to prevent 'pkg build' from writing the
PKG_ADD/PKG_DEL directives in the PKG_ADD/PKD_DEL files that are bundled into
the binary package tarball. Otherwise, these directives will end up being
duplicated (in two separate files, as it is currently the case, or in one
single file if we insist on having PKG_ADD/PKG_DEL files in only one place,
but this is not better).

Another solution would be to mark binary package tarballs as a special kind of
package tarball, for which PKG_ADD/PKG_DEL do not need to be processed during
'pkg install' (since they have been processed during 'pkg build'). In other
words, pkg should process PKG_ADD/PKG_DEL directives only when building a
binary tarball, or when building+installing from source, but *not* when
installing from a binary tarball.



    _______________________________________________________

Reply to this item at:

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

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