[PD-dev] new distro: pd-vanilla+libs

[Hans-Christoph Steiner]

One thing that I think should be different with this pd-vanilla  
distro is that it should be built against the latest libraries, like  
the latest Tcl/Tk.  That will smooth some things out with pd-vanilla,  
at least on Mac OS X.

On Mac OS X, the anti-aliasing is mostly an issue of which version of  
Tcl/Tk is using.

.hc

On Apr 18, 2008, at 7:53 PM, Brandon Zeeb wrote:

> 	Ah, np.  Perfect.  Is the lack of anti-aliasing in pd-vanilla a  
> purely vanilla issue, tcl/tk, or extensions to pd-extended?  Not a  
> slam, but I do prefer pd-extended's look.
>
> Cheers,
> ~Brandon
>
>
>
> On Apr 18, 2008, at 3:56 PM, Hans-Christoph Steiner wrote:
>
>>
>> pd-vanilla would be vanilla only, no patches to pd itself.  Pd- 
>> extended is for the patches.
>>
>> .hc
>>
>> On Apr 18, 2008, at 12:25 PM, bsoisoi wrote:
>>
>>> Could this also include the sexy gui?
>>>
>>> ~Brandon
>>>
>>>
>>> On Apr 18, 2008, at 12:16 PM, Hans-Christoph Steiner wrote:
>>>
>>>>
>>>> On Apr 18, 2008, at 8:46 AM, Frank Barknecht wrote:
>>>>
>>>>> Hallo Hans,
>>>>> Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner  
>>>>> wrote:
>>>>>> Now that Pd can be built on all platforms without patches, I  
>>>>>> think we
>>>>>> can have a "pd-vanilla+libs" distro that is based on an  
>>>>>> unpatched pd-
>>>>>> vanilla build.  It could also have a more limited subset of  
>>>>>> included
>>>>>> libraries, much like others have been proposing.  They would be
>>>>>> having the same library format and install methods as Pd- 
>>>>>> extended, so
>>>>>> that patches would be compatible.
>>>>>
>>>>> I think, this is a very good idea and I'll stick it on my TODO  
>>>>> list,
>>>>> however I believe, that instead of a vanilla+libs bundle a pure  
>>>>> "libs"
>>>>> installer/package would be more appropriate, kind of like the
>>>>> traditional pd-externals package. We already have binary  
>>>>> packages of
>>>>> vanilla Pd (Miller's and autobuild) and I believe it's easier  
>>>>> to get
>>>>> more people to use the same externals setup by providing a package
>>>>> independent from a certain Pd build.
>>>>
>>>> Ultimately, that sounds like a good goal, but it would also be a  
>>>> lot
>>>> more work, and would cuase more bugs.  There are incompatibilities
>>>> between versions, not always large, but there.  That means you'd  
>>>> then
>>>> have to add code to manage that.  Externals are a lot like linux
>>>> kernel modules.  Sure, it is possible to create module binaries  
>>>> that
>>>> work with different versions of the kernel, but the vast  
>>>> majority of
>>>> people choose to ship source, and only include binaries that are  
>>>> tied
>>>> to a specific kernel version.
>>>>
>>>> So it seems to me the thing to do is first get the one big build
>>>> working, then the people can split up the packages if they want.
>>>>
>>>> .hc
>>>>
>>>> ------------------------------------------------------------------- 
>>>> -----
>>>> ----
>>>>
>>>> Access to computers should be unlimited and total.  - the hacker  
>>>> ethic
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> PD-dev mailing list
>>>> PD-dev at iem.at
>>>> http://lists.puredata.info/listinfo/pd-dev
>>
>>
>>
>> --------------------------------------------------------------------- 
>> -------
>>
>> There is no way to peace, peace is the way.       -A.J. Muste
>>
>>





------------------------------------------------------------------------ 
----

'You people have such restrictive dress for women,’ she said,  
hobbling away in three inch heels and panty hose to finish out  
another pink-collar temp pool day.  - “Hijab Scene #2", by Mohja Kahf