<HTML dir=ltr><HEAD><TITLE>Re: RPM Spec file that demonstrates the modularity of Smart</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText70938 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Right, there are a few ways to skin this particular cat. Right now the spec file method is implemented and, with caveats, works. Once one of these other methods is implemented it would be unnecessary to do it.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Anders F Björklund [mailto:afb@algonet.se]<BR><B>Sent:</B> Sun 15/02/2009 20:45<BR><B>To:</B> rehan khan<BR><B>Cc:</B> smart@labix.org<BR><B>Subject:</B> Re: RPM Spec file that demonstrates the modularity of Smart<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>rehan khan wrote:<BR><BR>> The there is no direct purpose as such and there is no problem with <BR>> the current packaging strategy. It started out as an exercise in <BR>> getting access to the ok button on smaller screen sizes on the add <BR>> channel dialog (by reducing the number of installed options).<BR><BR>There are other ways to make the New Channel dialog work, for instance<BR>putting the list of channel types in a scrollable list or popup menu...<BR><BR>--anders<BR><BR><BR><BR></FONT></P></DIV></BODY></HTML>