2012/3/25 Carnë Draug <carandraug+...@gmail.com>: > On 25 March 2012 11:43, c. <carlo.defa...@gmail.com> wrote: >> I see 3 possibilities to fix this: >> >> 1 - change the PKG_ADD in the packages >> >> 2 - patch pkg.m to handle subdirectories in a better way >> >> 3 - forbid the use of subdirectorues in packages >> >> I personally don't like the third solution, what would you prefer? > > The idea of having this subdirectories is a matter of organization for > the package developers right? (Since upon package installation, the > user can only load either all or none of the package anyway). If > that's the case, I'll suggest a 4th option (maybe only temporary while > we can't anything better) that is to have all the subpackages in a > inst/ directory. The source tree can differ from the tree of the > actual release, I believe that is acceptable. > > Carnë
Hi, That is how I started. somehow I changed to the PKG_ADD option as in ocs. It looks cleaner. However, I have no arguments against this 4th option, except for aesthetics. So, what is going to be? Also, the subpackages idea still suffers from the problem that each package can bring its own makefile and I haven't yet solved the issue of merging them or creating a global makefile that will call each makefile independently. -- M. Sc. Juan Pablo Carbajal ----- PhD Student University of Zürich http://ailab.ifi.uzh.ch/carbajal/ ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
