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

[Philip Nienhuis]

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

@Julien, comment #7:
I never heard of PKG_ADD / PKG_DEL directives, I haven't found documentation
for it either - but I had no reason to search. So there's my motive.

What advantage do such directives have over what Carnë (below in pt. 2 & 3)
and I suggest?
If there's a use case for directives with clear advantages over Carnë's/my
suggestion, well let's keep them. If not I'd opt for the simplest solution,
for the reasons I already described.

The other thing is that we have some legacy of existing packages. How are we
going to cope with them?


@Carnë, comment #8 item 8: 
binary modules and m-files get lumped together when installing packages in
Linux HOME dirs, e.g., for io I get:

~/octave/io-2.2.8: all m-files
~/octave/io-2.2.8/x86_64-unknown-linux-gnu-api-v50+: all .oct files


so the binary modules reside in a subdir of the arch-independent files.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/