Re: tarball and unpacked top directory name syncronization

2007-08-28 Fir de Conversatie Per Hallsmark
Bram Moolenaar wrote: Sorry, but I don't see why a decent build script would require the source to be packaged in a specific way. Yes, it would be simpler if they all use the same convention, but you cannot depend on that. A descent designed code tries not to duplicate stuff

Re: tarball and unpacked top directory name syncronization

2007-08-20 Fir de Conversatie Matthew Woehlke
Try #4... Bram Moolenaar wrote: Per Hallsmark wrote: Is it possible to have this reworked so that vim follows same scheme as about 99% of the rest of the world does? :) A change like this will break existing build scripts. Alternatively, a change like this will allow existing build

Re: tarball and unpacked top directory name syncronization

2007-08-20 Fir de Conversatie Bram Moolenaar
Matthew Woehlke wrote: Try #4... Bram Moolenaar wrote: Per Hallsmark wrote: Is it possible to have this reworked so that vim follows same scheme as about 99% of the rest of the world does? :) A change like this will break existing build scripts. Alternatively, a change like

RE: tarball and unpacked top directory name syncronization

2007-08-11 Fir de Conversatie Suresh Govindachar`
Per [...] Per Per Most opensource packages are named like proj- Per version.tar.gz, or bz2 for that matter. After Per uncompress/untar, the top directory is similar to tarball Per without extensions proj-version. Per Per [...] Per Per Unfortunally, when uncompressing and