<div>I know this goes against slack packaging standards, and that I'll probably get my a** flamed, but back before we had vim 7.0 I had made a vim7 package... the binary was called vim7, and I put it in /usr/local/bin (and properly documented in the slack-desc why it was put there)
</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 9/21/06, <b class="gmail_sendername">Alan Hicks</b> <<a href="mailto:alan@lizella.net">alan@lizella.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Grant wrote:<br>> I'd like to speed up vim, take out bidi char support, English only, make it<br>> into lighter weight editor -- vim
7.0 is noticeably slower then vim 6.3 on<br>> firewall box (p-mmx/233MHz + 128MB memory)<br><br>In general we have a rule not to accept build scripts for software<br>that's already included in Slackware unless there's a compelling reason
<br>(apache-2 vs. apache-1.3 for example). I'm not sure what others will<br>say as to this particular issue. In general, the rule is sorta applied<br>case-by-case. I personally see a few problems and I'll just go ahead
<br>and air them out here.<br><br>1- Is it really that big a deal? If the answer is "yes", well, I won't<br>object.<br>2- Assuming we decide to include it, how will we name it? vim-6.3?<br>vim-6.3-lightweight? vim-slim?
<br>3- Would it interfere with the default Slackware vim in any way? I'm<br>sure this can be addressed by renaming the binary vim-6.3 or something.<br>The user can setup his own alias, or change the vi symlink.<br>4- Make sure that the changes from the default Slackware package are
<br>well documented, including mentioning any features that are present in<br>the default package, but not in this build.<br>5- The doinst.sh package shouldn't screw with the default Slackware vim<br>package or any of its add-ons (like gvim), and it should be thoroughly
<br>tested to ensure that it doesn't screw up anything like gvim. This is a<br>big stickler for me. Even if the others are addressed to my liking, I<br>won't sign my name to the script(s) if it doesn't pass this rule.<br>
<br>If you think you can solve those satisfactorily (and I see no reason why<br>you couldn't), then I think you should get to work. :^)<br><br>--<br>It is better to hear the rebuke of the wise,<br>Than for a man to hear the song of fools.
<br>Ecclesiastes 7:5<br><br><br><br>_______________________________________________<br>Slackbuilds-users mailing list<br><a href="mailto:Slackbuilds-users@slackbuilds.org">Slackbuilds-users@slackbuilds.org</a><br><a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br><br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Martin Lefebvre<br>eMail: <a href="mailto:dadexter@gmail.com">dadexter@gmail.com</a><br>
<br>WWW: <a href="http://sigterm.homeunix.com">http://sigterm.homeunix.com</a><br>Registered Linux #349269<br><br>"Me? I'm dishonest, and a dishonest man you can always trust to<br>be dishonest. Honestly. It's the honest ones you want to watch
<br>out for, because you can never predict when they're going to do<br>something incredibly... stupid."