Hey all,
Since the pd-externals package is no longer included in Debian, then it's probably ok to widdle away at the stuff that's included in the externals/build/src (aka "flatspace") section.
Wadaya all think? Any objections? A couple people have already started this...
.hc
------------------------------------------------------------------------ ----
Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism. - retired U.S. Army general, William Odom
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Since the pd-externals package is no longer included in Debian, then it's probably ok to widdle away at the stuff that's included in the externals/build/src (aka "flatspace") section.
What does the Debian package have to do with flatspace?
Ciao
On Nov 22, 2007, at 2:18 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Since the pd-externals package is no longer included in Debian, then it's probably ok to widdle away at the stuff that's included in the externals/build/src (aka "flatspace") section.
What does the Debian package have to do with flatspace?
The Debian package pd-externals was built from the "externals/build/ src" build system Günter set up years ago. The "flatspace" lib in Pd- extended is the contents of that build system.
.hc
------------------------------------------------------------------------ ----
Computer science is no more related to the computer than astronomy is related to the telescope. -Edsger Dykstra
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
What does the Debian package have to do with flatspace?
The Debian package pd-externals was built from the "externals/build/ src" build system GÃŒnter set up years ago. The "flatspace" lib in Pd- extended is the contents of that build system.
I know that both flatspace and the pd-externals deb are using the old build system, but I don't see how the existence or non-existence of the deb would influence the existence of flatspace in pd-extended. Maybe it has to do with some quantum physics entanglement issue, I didn't understand? ;)
Anyway if all externals from flatspace are also included in other subdirectories of pd-extended then I don't see why pd-extended would need a flatspace. But I'm no pd-extended user, so probably someone else should comment.
Ciao
Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
What does the Debian package have to do with flatspace?
The Debian package pd-externals was built from the "externals/build/ src" build system GÃŒnter set up years ago. The "flatspace" lib in Pd- extended is the contents of that build system.
I know that both flatspace and the pd-externals deb are using the old build system, but I don't see how the existence or non-existence of the deb would influence the existence of flatspace in pd-extended. Maybe it has to do with some quantum physics entanglement issue, I didn't understand? ;)
Anyway if all externals from flatspace are also included in other subdirectories of pd-extended then I don't see why pd-extended would need a flatspace. But I'm no pd-extended user, so probably someone else should comment.
I use pd-extended and I think it would be a lot easier to use if _everything_ was in flatspace so I don't have to rewrite all my objects with the directory prefix and manually track down the help files. For example all the stuff in mrpeach could just as easily be in flatspace since none of it depends on anything else, there is no library file they all need except for pd itself. If any name conflicts arise I would just rename the offending objects. (Also I think the proper term is "whittling" which is like shaving wood from a stick, not "widdling" which is like urinating in a dribbly fashion ;))
Martin
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
I use pd-extended and I think it would be a lot easier to use if _everything_ was in flatspace so I don't have to rewrite all my objects with the directory prefix and manually track down the help files. For example all the stuff in mrpeach could just as easily be in flatspace since none of it depends on anything else, there is no library file they all need except for pd itself. If any name conflicts arise I would just rename the offending objects.
That actually was the approach of the original, pre-pd-extened build system in the CVS: Instead of including all versions of an objectclass name, only one would be chosen to be included in the build system and in releases. Pd-extended instead opted to use a build and packaging system that could include all versions of, say, [gate] , but put them in different subdirectories. The side effect is that now everything is in subdirectories and it's hard to tell, which [gate] you mean if you just write [gate].
Ciao
On Nov 25, 2007, at 5:44 PM, Frank Barknecht wrote:
Hallo, Martin Peach hat gesagt: // Martin Peach wrote:
I use pd-extended and I think it would be a lot easier to use if _everything_ was in flatspace so I don't have to rewrite all my objects with the directory prefix and manually track down the help files. For example all the stuff in mrpeach could just as easily be in flatspace since none of it depends on anything else, there is no library file they all need except for pd itself. If any name conflicts arise I would just rename the offending objects.
That actually was the approach of the original, pre-pd-extened build system in the CVS: Instead of including all versions of an objectclass name, only one would be chosen to be included in the build system and in releases. Pd-extended instead opted to use a build and packaging system that could include all versions of, say, [gate] , but put them in different subdirectories. The side effect is that now everything is in subdirectories and it's hard to tell, which [gate] you mean if you just write [gate].
And that's why patch-local library loading was added in 0.40. Then you know which libraries are loaded because you can just look at the [import] or [declare] statement.
If you don't want to use namespace prefixes, then you can just use the default preferences, which loads basically every library into the global namespace.
.hc
------------------------------------------------------------------------ ----
News is what people want to keep hidden and everything else is publicity. - Bill Moyers