On Mar 17, 2009, at 2:02 PM, Per Øyvind Karlsen wrote:
Yeah. you're right, I've had that thought myself more than once
already, but my initial focus has been to just do something simple,
fairly minimal and working before making it into something nice and
sane in addition.
Using libcpui
2009/3/17 Jeff Johnson
> The DOOM (from aliasing) starts right here ...
>
> Your desire & approach to "compatibility" is sound, what's wrong is
> compiling the
> bleeping strings into RPM. That's basically what rpmrc files achieved,
> having
> strings & number identifiers out of RPM code.
>
> Not
On Tue, Mar 17, 2009 at 5:36 PM, Jeff Johnson wrote:
> Oooh, thank you! I keep meaning to do this ...
>
> BTW, perhaps its time to switch RPM to using Gnulib
> for portability issues as suggested (for popt) here:
>
>http://rpm5.org/community/rpm-devel/3161.html
>
> (aside)
> I plain and s
The DOOM (from aliasing) starts right here ...
Your desire & approach to "compatibility" is sound, what's wrong is
compiling the
bleeping strings into RPM. That's basically what rpmrc files achieved,
having
strings & number identifiers out of RPM code.
Note that rpmrc was an exceedingly gro
Oooh, thank you! I keep meaning to do this ...
BTW, perhaps its time to switch RPM to using Gnulib
for portability issues as suggested (for popt) here:
http://rpm5.org/community/rpm-devel/3161.html
(aside)
I plain and simply __CANNOT__ justify Gnulib for popt
for the two dinky portabili
