Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]

2007-05-18 Thread Stephan Hegel

Hi,

Ali Akcaagac wrote:
A lot of the readers here als prefer lftp as good choice for 
ftp'ing.

Well, since I do use ncftp anyway on several platforms I've
got ncftpget for free and so the posted approach is perfectly
fine for me. I don't speak for others, of course, just trying
to show and share a neat solution.

Your two lines of getting the patches is indeed nice. 

It is only one line ;). Similar like your wget approach in
getvim.sh:
   ncftpget ftp.vim.org . '/pub/editors/vim/patches/7.1/7.1.*'

So my fully-automatic build - this has been my goal - looks
now like this (snippet from the Makefile):

all:
tar xfj vim-7.1.tar.bz2
tar xfz vim-7.1-lang.tar.gz
tar xfz vim-7.1-extra.tar.gz
(cd vim-7.1.patches ; ncftpget ftp.vim.org . 
'/pub/editors/vim/patches/7.1/7.1.*')
cat vim-7.1.patches/7.1.*  patchfile
(cd vim71 ; patch -p0  ../patchfile)
(cd vim71 ; ./configure --prefix=$(PREFIX) --with-x
--enable-gui=gtk2 --enable-multibyte --enable-xim --enable-fontset
--enable-perlinterp --enable-cscope  make)



Can also be done with wget only. Please allow me to remind the people
here on the getvim script that I once wrote. It collect all patches 
and made one huge patchfile out of it. Quite trivial to use.

Using one huge patchfile is also my approach as you can see
above and on Unix/Linux systems this can be done with a simple
cat 7.1.*  patchfile 'cause the right sorting order is already
built-in. If somebody has got another experience with, e.g.
different locale settings, I would appreciate to know.

As Tony has pointed out already, this doesn't work on Dos /
Windows as the sorting order seems to be different there,
unfortunately.


http://www.akcaagac.com/tools/files/shell/getvim.sh

I had a look: interesting and new to me is your approach with
seq. I'll remember this when I need a sequence of formatted,
ascending numbers in a shell script. But for creating the vim
patchfile with all patches included it is overdone, IMO. In this
case you even need to edit the script with every new patch (see:
$SUBLEVELEND). Plus you still need to apply the patch and build
manually.

Kind regards,
  Stephan.




Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]

2007-05-17 Thread Stephan Hegel

Hi,

A.J.Mechelynck wrote:
- Using cat is OK as long as you can be sure that you'll get them in 
numeric order: this is usually the case on Unix but not necessarily on 
Dos, where a wildcarded filename usually gets its results in directory 
order, not sorted by filename.

Well, you are right: I'm on Linux and wasn't aware of the different DOS
sorting order. So, the following below applies to Linux/Unix only ...

- By patching individually, if one of the patches fails horribly you may 
decide not to try the following.
- Usually there aren't more than a handful of _new_ patches anyway, so 
(except when starting from scratch with many patches already published) 
it's hardly worth the trouble going to a cat step.

What you have described even on your Web page, IMHO still too much manual
work. After downloading new patches with ncftp I just type make all
with the following Makefile:

-
PREFIX=/usr/local

help:
@echo Available targets:
@echoall
@echoinstall
@echoclean

all: clean
tar xfj vim-7.1.tar.bz2
tar xfz vim-7.1-lang.tar.gz
tar xfz vim-7.1-extra.tar.gz
cat vim-7.1.patches/7.1.*  patchfile
(cd vim71 ; patch -p0  ../patchfile)
(cd vim71 ; ./configure --prefix=$(PREFIX) --with-x --enable-gui=gtk2
--enable-multibyte --enable-xim --enable-fontset --enable-perlinterp
--enable-cscope  make)

install:
(cd vim71; umask 022; installwatch -o 
/home/steve/install.log/vim-7.1.log make install)
chmod 644 /home/steve/install.log/vim-7.1.log

clean:
rm -rf patchfile
rm -rf vim71

.PHONY: help all install clean
--

... and everything is done in less than 150 sec. Works for me for a long
time and starting from scratch keeps me out of trouble with old objects,
etc. Should not happen with make ... yes, this is what optimists always
say, but there is still Murphy ;).

BTW, make should stop when patch or any other action fails.

Interesting would  be an extension to download the patches automagically.
Comments  ideas ?

Regards,
  Stephan.


Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]

2007-05-17 Thread Stephan Hegel

A.J.Mechelynck wrote:
- What is ncftp? On my openSUSE 10.2 system I have a program called 
ftp but none called ncftp.

[39]./home/steve: rpm -qi ncftp
Name: ncftpRelocations: (not relocatable)
Version : 3.1.9 Vendor: SUSE LINUX Products 
GmbH, Nuernberg, Germany
Release : 2 Build Date: Fri 09 Sep 2005 
06:15:16 PM CEST
Install date: Sun 16 Oct 2005 06:07:57 AM CEST  Build Host: berlioz.suse.de
Group   : Productivity/Networking/Ftp/Clients   Source RPM: 
ncftp-3.1.9-2.src.rpm
Size: 1038391  License: Artistic License
Signature   : DSA/SHA1, Fri 09 Sep 2005 06:52:45 PM CEST, Key ID 
a84edae89c800aca
Packager: http://www.suse.de/feedback
URL : http://www.ncftp.com/
Summary : A Comfortable FTP Program
Description :
This program has been in service on UNIX systems since 1991 and is a
popular alternative to the standard FTP program, /usr/bin/ftp. NcFTP
offers many ease-of-use and performance enhancements over the stock FTP
client, and runs on a wide variety of UNIX platforms as well as
operating systems such as Microsoft Windows and Apple Mac OS X.



Authors:

Mike Gleason [EMAIL PROTECTED]
Distribution: SUSE LINUX 10.0 (i586)



Regards,
  Stephan.


Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]

2007-05-17 Thread Stephan Hegel

A.J.Mechelynck wrote:
Well, AFAICT it has disappeared between SuSE 10.0 and 10.2. 

No, my copy of Suse 10.2 contains the package:

[18]/media/dvdram/suse/i586: rpm -qip ncftp-3.2.0-17.i586.rpm
Name: ncftp Relocations: (not relocatable)
Version : 3.2.0 Vendor: SUSE LINUX Products GmbH, 
Nuernberg, Germany
Release : 17Build Date: Sun 26 Nov 2006 
03:50:45 AM CET
Install date: (not installed)   Build Host: fix.suse.de
Group   : Productivity/Networking/Ftp/Clients   Source RPM: 
ncftp-3.2.0-17.src.rpm
Size: 1069921   License: Artistic License
Signature   : DSA/SHA1, Sun 26 Nov 2006 03:51:52 AM CET, Key ID a84edae89c800aca
Packager: http://bugs.opensuse.org
URL : http://www.ncftp.com/
Summary : A Comfortable FTP Program
Description :
This program has been in service on UNIX systems since 1991 and is a
popular alternative to the standard FTP program, /usr/bin/ftp. NcFTP
offers many ease-of-use and performance enhancements over the stock FTP
client and runs on a wide variety of UNIX platforms as well as
operating systems like Microsoft Windows and Apple Mac OS X.

Authors:

Mike Gleason [EMAIL PROTECTED]
Distribution: openSUSE 10.2 (i586)


In case you have the six-CD version, the following note at www.opensuse.org
could explain why you don't have it: Due to size limitations of CD images, you
get only a subset of all packaged software for openSUSE.

But then you should be able to fetch the missing packages from ftp.opensuse.org.

Rgds,
  Stephan.




Re: [Fwd: Re: compiling vim7.1 (huge version) gets build with normal version]

2007-05-17 Thread Stephan Hegel

scott wrote:
a visit to yast, software management, searched for ncftp and it 
brought ncftp right to the fore, installed it for me, and i've been 
happily learning features since -- imagine commandline recall that 
works in ftp!  bookmarks!

And I just figured out that it comes with an utility called ncftpget:
So
   ncftpget ftp.vim.org . '/pub/editors/vim/patches/7.1/7.1.*'
fetches all patches to the local directory in one go.

And it does it in a smart way, see the second try:
   ncftpget ftp.vim.org . '/pub/editors/vim/patches/7.1/7.1.*'
   ncftpget /pub/editors/vim/patches/7.1/7.1.*: local file appears
  to be the same as the remote file, download is not necessary.

Perfect for running from a build script. That is what I have been
looking for.

One more big plus: besides for almost all sorts of Un*x, ncftp is
available for Windows as well.

Rgds,
  Stephan.