[L2Ork-dev] New Pd-L2Ork release

[Ivica Bukvic]

This is mainly because I stopped using the regular - F build system quite
some time ago. I am sorry I did not know you were using that for staging on
your end. What I would suggest is instead dropping the - F path and
focusing on the -B where we can define an additional variable by which you
could prevent that last step on your end and in other places where this its
command is not available or practical. What do you think?

As an example of this, look into how I prevent rebuilding the gem package
which takes quite a bit of time when using the -b incremental build. I use
for this purpose the variable defined in tar_me_up.sh in the
externals/Makefile

Hope this helps!

-- 
Ivica Ico Bukvic, D.M.A.
Associate Professor
Computer Music
ICAT Senior Fellow
Director -- DISIS, L2Ork
Virginia Tech
School of Performing Arts – 0141
Blacksburg, VA 24061
(540) 231-6139
ico at vt.edu
www.performingarts.vt.edu
disis.icat.vt.edu
l2ork.icat.vt.edu
ico.bukvic.net
On Jun 16, 2016 18:07, "Albert Graef" <aggraef at gmail.com> wrote:

> On Thu, Jun 16, 2016 at 9:52 PM, Ivica Ico Bukvic <ico at vt.edu> wrote:
>
>> I seem to recall that taking place in one of the scripts as it was not
>> included by default. grep may shed some light onto that. I am surprised,
>> however, that it does not work via autobuild [...]
>
>
> Yeah, found it, it's in the linux_make 'deb' target. There's a bunch of
> extra staging being done there (linux_make/Makefile:90-156). None of that
> will be done when creating a tarball package with './tar_em_up.sh -F',
> which is basically what I'm doing in my packaging scripts. (Note that I
> can't use the 'make deb' part because in the end it runs dpkg-deb which is
> of no use with debuild, and doesn't work on Arch at all).
>
> So what I need to do right now basically is to replicate the staging
> that's being done at the beginning 'make deb'. Which isn't really a problem
> (I've been doing that all along), but of course I need to keep that in sync
> with your 'make deb' target. As a case in point, it seems that the arduino
> folder was added recently to 'make deb' and I haven't picked that up yet. I
> can (and will) fix that, of course.
>
> But, in order to make things easier for 3rd party package maintainers like
> me, maybe the beginning of 'make deb' could be moved into the linux_make
> 'make install'? I wonder why this isn't the case to begin with. Is there a
> good reason to keep all that extra stuff in the "Burrito Supreme" Debian
> package out of the tarball package?
>
> Albert
>
> --
> Dr. Albert Gr"af
> Computer Music Research Group, JGU Mainz, Germany
> Email:  aggraef at gmail.com
> WWW:    https://plus.google.com/+AlbertGraef
>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/listinfo/l2ork-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20160616/5b909b17/attachment.html>