On Thu, Feb 26, 2009 at 11:48:25AM +0100, Remy Bohmer wrote:
> > You need to make the *packet* tristate, not the feature-options in
> > the "if" part. There is some magic that correlates the packet labels
> > (name in capital letters) to the packet names. So instead of your
> > ... you should make
Hello Robert,
> You need to make the *packet* tristate, not the feature-options in the
> "if" part. There is some magic that correlates the packet labels (name
> in capital letters) to the packet names. So instead of your ...
> you should make one in file per application and, if you want to, put
>
On Wed, Feb 25, 2009 at 10:01:40PM +0100, Remy Bohmer wrote:
> I am using the ptxdist version 1.99.11 and/or trunk(rev-9842) with the
> new collection config feature.
Ah, great!
> What I am trying to achieve here is to build 2 configurations out of 1
> userland ptxconfig file, namely a small-rele
Remy Bohmer wrote:
> Hello All,
>
> I am using the ptxdist version 1.99.11 and/or trunk(rev-9842) with the
> new collection config feature.
> What I am trying to achieve here is to build 2 configurations out of 1
> userland ptxconfig file, namely a small-release image, and a
> full-blown debug-ima
Hello All,
I am using the ptxdist version 1.99.11 and/or trunk(rev-9842) with the
new collection config feature.
What I am trying to achieve here is to build 2 configurations out of 1
userland ptxconfig file, namely a small-release image, and a
full-blown debug-image.
Packages that only need to go
