On Thu, Apr 22, 2010 at 7:28 PM, wen heping wenhep...@gmail.com wrote:
Are you working on scilab-5.2.2 ?
wen
Yes - it builds and I got the ocaml issues worked out too, I just need
to do a little bit of testing and I should have something to submit
later today or tomorrow.
--
Rob Farmer
to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way to make one?
You normally base it on the output of
${FIND} -s PATH -type f
${FIND} -d PATH -type d | ${SED} 's,^,@dirrm ,'
Of course there's normally more to it, but that's the basic principle
of a pain to
update. The porters handbook makes vague reference to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way to make one?
You normally base it on the output of
${FIND} -s PATH -type f
${FIND} -d PATH -type d | ${SED} 's,^,@dirrm
to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way to make one?
The reference is vague probably because static plists are generally
preferred. :-) But you can start by studying ports that pipe to
${TMPPLIST}; grep through the tree to find them. Also
. It is a bit of a pain to
update. The porters handbook makes vague reference to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way to make one?
You normally base it on the output of
${FIND} -s PATH -type f
${FIND} -d PATH -type d | ${SED} 's,^,@dirrm
), hundreds of which change
depending on what options are selected. It is a bit of a pain to
update. The porters handbook makes vague reference to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way to make one?
You normally base it on the output
it. This port has a
huge plist (slightly under 15000 lines), hundreds of which change
depending on what options are selected. It is a bit of a pain to
update. The porters handbook makes vague reference to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way
, Rob Farmer wrote:
I maintain math/scilab and am preparing to update it. This port has a
huge plist (slightly under 15000 lines), hundreds of which change
depending on what options are selected. It is a bit of a pain to
update. The porters handbook makes vague reference to dynamic plists
options are selected. It is a bit of a pain to
update. The porters handbook makes vague reference to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way to make one?
You normally base it on the output of
${FIND} -s PATH -type f
${FIND} -d PATH
Hi,
I maintain math/scilab and am preparing to update it. This port has a
huge plist (slightly under 15000 lines), hundreds of which change
depending on what options are selected. It is a bit of a pain to
update. The porters handbook makes vague reference to dynamic plists -
so I was wondering
to dynamic plists -
so I was wondering, would this be a good idea? And if so, what is the
best way to make one?
The reference is vague probably because static plists are generally
preferred. :-) But you can start by studying ports that pipe to
${TMPPLIST}; grep through the tree to find them. Also
11 matches
Mail list logo
