> > I am on Gentoo-Linux, which I freshly installed a month ago. With > > > the Gentoo system I had previously I experimented with pd-overlay > > > and ebuilds, which are not supported by the Gentoo crew, which tends > > > to make things more complicated than easier. > > > The current system has to last longer than the previous one, so I > > > willl no longer unmask packages or install overlays and ebuilds > > > from other sources than from the Gentoo-crew itsself. > > > > > > In case of the need to install things not supported by the > > > Gentoo-crew those have to compile out-of-the-box (classical way > > > of installing which only system dependency is of "being on > > > a linux box" instead of makeing diffderences what distribution > > > is used.) > > > > > > By the way: pd-extended searches for dpkg-* executables and than > > > thinks of being on Debian and installs everything into /usr/bin > > > instead of /usr/local/bin. > > > My opinion is, that this logic is not working in every case. Gentoo > > > offers dpkg-* utils also. The result is that pd-extended gets > > > installed into places, which are only for ebuilds. > > > (Takes me some time to figure out, whether everything wants > > > to go to /usr...) > > > As long as there are no official ebuilds for Gentoo, pd-extended > > > should keep its fingers off /usr. > > > If the distribution cannot figured out 100% surely, break the > installation > > > process or ask the user for help. > > > The existence or not-existence of certain tools is not strong logic. > > > > > > Only my two cents, your currency may vary... ;) > > > > > > --- > > > > > > I compiled pd-0.42-5 from the link you gave me, and it > > > compiles/installes well. > > > Unfortunately I have no clue, how install the rest, which makes the > > > now installed pd-vanilla into pd-extended... > > > > > > > > http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/ > > Here you can download several external libraries. Some may install easy, > > some may not. That's why the community came up with the 'template' (also > in > > the externals-folder) to create a standard for libraries. Maybe in > somewhere > > future all libraries will install the same way. > > It's a hell of a job to install all libraries pd-extended contains, but I > > guess there's no need for that. Pd-extended loads a bunch of externals > every > > time you'll probably never use. It's easy though to have them all > installed > > but personally I seemed to use almost only vanilla-objects. Since I use > the > > same version you just installed I even know better what's available for > pd. > > The only disadvantage of not having pd-extended I can think of is when > you > > download someone else's patch and the only information you get is that > all > > objects are included in pd-extended. > > > > So whether you can use it the way as described above or you can try to > > change the install-path of pd-extended and uninstall pd-vanilla again. > > For the last option: searching somewhere in the source for "/usr/bin/" > and > > change that bit of text to "usr/local/bin" is what I would try in your > > position. > > mfg > > Funs > > No! Stop...I will NOT search through the source to get something > instaled which is called"stable" or "release code" to get a hint how > install the whole stuff. I am no developper (in this case). I am a > user. The trouble starts, where a faulty packaege is detected late in > the __installation phase__ of the makefile system, urging the user to > gues the way back to the failure inducing problem. > Soryy guys...I quit. > > Nothing to be sorry for. It's up to you what software you use. mfg Funs
> Bye, > Best regards, > mcc > > > >
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list