Hey,
I am planning on importing all of the sources needed to build Pd- extended on Windows into a new section of the pure-data CVS. Right now, there is no management, and it's a mess. This way, all the random scripts needed to build all those sources can also be checked in there. Also, it will be much easier to manage the small tweaks needed to get somethings building properly.
Luckily, CVS is designed to do this:
"13. Tracking third-party sources" http://ximbiot.com/cvs/manual/cvs-1.12.9/cvs_13.html
I am not particular about the name of the section, I am thinking "win32_sources". Comments, feedback, etc.?
.hc
------------------------------------------------------------------------ ----
Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies. - Amy Smith
Hans-Christoph Steiner wrote:
Hey,
hi
Luckily, CVS is designed to do this:
"13. Tracking third-party sources" http://ximbiot.com/cvs/manual/cvs-1.12.9/cvs_13.html
;-) my only comment on this is that i won't comment it.
I am not particular about the name of the section, I am thinking "win32_sources". Comments, feedback, etc.?
so what happens if (after some time) you notice that other OS's will profit from the packages in win32_sources too? will the package "foobar" live in both "win32_sources" and "linux64_sources"? or will the linux-stuff also live in "win32_sources"?
i'd rather vote for "3rdparty" or something along these lines.
mfg.asdr IOhannes
On Apr 25, 2007, at 11:04 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
Hey,
hi
Luckily, CVS is designed to do this:
"13. Tracking third-party sources" http://ximbiot.com/cvs/manual/cvs-1.12.9/cvs_13.html
;-) my only comment on this is that i won't comment it.
I am not particular about the name of the section, I am thinking "win32_sources". Comments, feedback, etc.?
so what happens if (after some time) you notice that other OS's will profit from the packages in win32_sources too? will the package "foobar" live in both "win32_sources" and "linux64_sources"? or will the linux-stuff also live in "win32_sources"?
i'd rather vote for "3rdparty" or something along these lines.
I am fine with a different name.
But I have to say, I think we should try to avoid using these sources for anything else but Win32. Right now, the policy with the auto- build farms is that the deps need to be in that platform's package management. MinGW has no package management beyond the basic tools, hence this repository.
.hc
mfg.asdr IOhannes
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
Mistrust authority - promote decentralization. - the hacker ethic