From: Earnie B. <ear...@ya...> - 2002-11-05 13:01:51
|
I've added manubee to the list of developers and have associated ma...@us... with the mingw-dvlpr mailing list. If you wish to post messages with a different account please let me know. Work with Kees on the package layout. The ports subdirectory has already been added but is empty. I will look at the web pages to decide what/how w.r.t. promoting MinGW ports. The MinGW ports maintenance, implementation and distribution belong to you and Kees. Have fun, Earnie. Manu wrote: > My experimental grep 2.5 is ready to be committed to MinGW ports > if you wish. > > Manu. > > ----- Original Message ----- > From: "Manu (mingw-users)" <min...@li...> > To: "mingw-users" <min...@li...> > Cc: <gnu...@us...> > Sent: Friday, November 01, 2002 7:54 AM > Subject: Re: [Mingw-users] Re: Grep 2.5 for MinGW > > > >>Earnie Boyd wrote: >>[cut] >> >>>This sounds much like a MinGW ports project. Manu and Kees, I can give >>>you access to the MinGW CVS, create a ports subdirectory for these types >>>of files. >>> >>>Interested? >> >>:) Yes, very interested. >> >>Though, I must remind that I'm a beginner in such >>exercises. I will still have a few (silly) questions to post. >> >>You've been warned :] >> >>Manu. >> >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by: See the NEW Palm >>Tungsten T handheld. Power & Color in a compact size! >>http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en >>_______________________________________________ >>MinGW-users mailing list >>Min...@li... >> >>You may change your MinGW Account Options or unsubscribe at: >>https://lists.sourceforge.net/lists/listinfo/mingw-users > > |
From: Kees Z. <kz...@us...> - 2002-11-05 18:47:17
|
A suggestion on how to further subdivide the ports subdirectory: It might be divided according to package (e.g. grep) and these further divided according to version numbers (e.g. 2.5). At this second level, in the example ports/grep/2.25, we might have at least a subdirectory mingw-patches, which contains the patch or patches to the original sources needed to compile the package with mingw and the autotools (thus under msys or cygwin). If binaries and patched sources would be provided, then these could go into subdirectories bin and src, and the compiled docs (chm, htm, pdf) into a subdirectory doc. Would this be agreeable? Kees ----- Oorspronkelijk bericht ----- Van: "Earnie Boyd" <ear...@ya...> Aan: "Manu" <con...@wa...> CC: "Kees Zeelenberg" <kz...@us...>; <min...@li...> Verzonden: dinsdag 5 november 2002 14:01 Onderwerp: Re: Fw: [Mingw-users] Re: Grep 2.5 for MinGW > I've added manubee to the list of developers and have associated > ma...@us... with the mingw-dvlpr mailing list. If you > wish to post messages with a different account please let me know. > > Work with Kees on the package layout. The ports subdirectory has > already been added but is empty. I will look at the web pages to decide > what/how w.r.t. promoting MinGW ports. The MinGW ports maintenance, > implementation and distribution belong to you and Kees. > > Have fun, > Earnie. > > Manu wrote: > > My experimental grep 2.5 is ready to be committed to MinGW ports > > if you wish. > > > > Manu. > > > > ----- Original Message ----- > > From: "Manu (mingw-users)" <min...@li...> > > To: "mingw-users" <min...@li...> > > Cc: <gnu...@us...> > > Sent: Friday, November 01, 2002 7:54 AM > > Subject: Re: [Mingw-users] Re: Grep 2.5 for MinGW > > > > > > > >>Earnie Boyd wrote: > >>[cut] > >> > >>>This sounds much like a MinGW ports project. Manu and Kees, I can give > >>>you access to the MinGW CVS, create a ports subdirectory for these types > >>>of files. > >>> > >>>Interested? > >> > >>:) Yes, very interested. > >> > >>Though, I must remind that I'm a beginner in such > >>exercises. I will still have a few (silly) questions to post. > >> > >>You've been warned :] > >> > >>Manu. > >> > >> > >> > >> > >>------------------------------------------------------- > >>This sf.net email is sponsored by: See the NEW Palm > >>Tungsten T handheld. Power & Color in a compact size! > >>http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > >>_______________________________________________ > >>MinGW-users mailing list > >>Min...@li... > >> > >>You may change your MinGW Account Options or unsubscribe at: > >>https://lists.sourceforge.net/lists/listinfo/mingw-users > > > > > |
From: Earnie B. <ear...@ya...> - 2002-11-05 19:01:25
|
Yes. Earnie. Kees Zeelenberg wrote: > A suggestion on how to further subdivide the ports subdirectory: It might be > divided according to package (e.g. grep) and these further divided according > to version numbers (e.g. 2.5). At this second level, in the example > ports/grep/2.25, we might have at least a subdirectory mingw-patches, which > contains the patch or patches to the original sources needed to compile the > package with mingw and the autotools (thus under msys or cygwin). If binaries > and patched sources would be provided, then these could go into subdirectories > bin and src, and the compiled docs (chm, htm, pdf) into a subdirectory doc. > Would this be agreeable? > > Kees > > ----- Oorspronkelijk bericht ----- > Van: "Earnie Boyd" <ear...@ya...> > Aan: "Manu" <con...@wa...> > CC: "Kees Zeelenberg" <kz...@us...>; > <min...@li...> > Verzonden: dinsdag 5 november 2002 14:01 > Onderwerp: Re: Fw: [Mingw-users] Re: Grep 2.5 for MinGW > > > >>I've added manubee to the list of developers and have associated >>ma...@us... with the mingw-dvlpr mailing list. If you >>wish to post messages with a different account please let me know. >> >>Work with Kees on the package layout. The ports subdirectory has >>already been added but is empty. I will look at the web pages to decide >>what/how w.r.t. promoting MinGW ports. The MinGW ports maintenance, >>implementation and distribution belong to you and Kees. >> >>Have fun, >>Earnie. >> >>Manu wrote: >> >>>My experimental grep 2.5 is ready to be committed to MinGW ports >>>if you wish. >>> >>>Manu. >>> >>>----- Original Message ----- >>>From: "Manu (mingw-users)" <min...@li...> >>>To: "mingw-users" <min...@li...> >>>Cc: <gnu...@us...> >>>Sent: Friday, November 01, 2002 7:54 AM >>>Subject: Re: [Mingw-users] Re: Grep 2.5 for MinGW >>> >>> >>> >>> >>>>Earnie Boyd wrote: >>>>[cut] >>>> >>>> >>>>>This sounds much like a MinGW ports project. Manu and Kees, I can give >>>>>you access to the MinGW CVS, create a ports subdirectory for these types >>>>>of files. >>>>> >>>>>Interested? >>>> >>>>:) Yes, very interested. >>>> >>>>Though, I must remind that I'm a beginner in such >>>>exercises. I will still have a few (silly) questions to post. >>>> >>>>You've been warned :] >>>> >>>>Manu. >>>> >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This sf.net email is sponsored by: See the NEW Palm >>>>Tungsten T handheld. Power & Color in a compact size! >>>>http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en >>>>_______________________________________________ >>>>MinGW-users mailing list >>>>Min...@li... >>>> >>>>You may change your MinGW Account Options or unsubscribe at: >>>>https://lists.sourceforge.net/lists/listinfo/mingw-users >>> >>> > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > |
From: Manu <ma...@wa...> - 2002-11-05 21:24:24
|
Kees Zeelenberg wrote: > A suggestion on how to further subdivide the ports subdirectory: It might be > divided according to package (e.g. grep) and these further divided according > to version numbers (e.g. 2.5). At this second level, in the example > ports/grep/2.25, we might have at least a subdirectory mingw-patches, So we would have 'ports/grep/2.5/mingw-patches'. Or maybe it could be simply ports/grep/2.5/patches or ports/grep/2.5/build in reference to build scripts. > which > contains the patch or patches to the original sources needed to compile the > package with mingw and the autotools (thus under msys or cygwin). If binaries > and patched sources would be provided, then these could go into subdirectories > bin and src, and the compiled docs (chm, htm, pdf) into a subdirectory doc. > Would this be agreeable? Yes, very good. Manu. |
From: Kees Z. <kz...@us...> - 2002-11-06 18:54:30
|
----- Oorspronkelijk bericht ----- Van: "Manu" <ma...@wa...> Aan: <min...@li...> Verzonden: dinsdag 5 november 2002 22:35 Onderwerp: Re: [MinGW-dvlpr] Re: Fw: [Mingw-users] Re: Grep 2.5 for MinGW > Kees Zeelenberg wrote: > > A suggestion on how to further subdivide the ports subdirectory: It might > be > > divided according to package (e.g. grep) and these further divided > according > > to version numbers (e.g. 2.5). At this second level, in the example > > ports/grep/2.25, we might have at least a subdirectory mingw-patches, > > So we would have 'ports/grep/2.5/mingw-patches'. > Or maybe it could be simply ports/grep/2.5/patches > or ports/grep/2.5/build > in reference to build scripts. > Yes, that would be fine. Kees > > which > > contains the patch or patches to the original sources needed to compile > the > > package with mingw and the autotools (thus under msys or cygwin). If > binaries > > and patched sources would be provided, then these could go into > subdirectories > > bin and src, and the compiled docs (chm, htm, pdf) into a subdirectory > doc. > > Would this be agreeable? > > Yes, very good. > Manu. > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > |
From: Manu <ma...@wa...> - 2002-11-06 21:14:44
|
Kees Zeelenberg wrote: > ----- Oorspronkelijk bericht ----- > Van: "Manu" > Aan: <min...@li...> > Verzonden: dinsdag 5 november 2002 22:35 > Onderwerp: Re: [MinGW-dvlpr] Re: Fw: [Mingw-users] Re: Grep 2.5 for MinGW > > > > Kees Zeelenberg wrote: > > > A suggestion on how to further subdivide the ports subdirectory: It might > > be > > > divided according to package (e.g. grep) and these further divided > > according > > > to version numbers (e.g. 2.5). At this second level, in the example > > > ports/grep/2.25, we might have at least a subdirectory mingw-patches, > > > > So we would have 'ports/grep/2.5/mingw-patches'. > > Or maybe it could be simply ports/grep/2.5/patches > > or ports/grep/2.5/build > > in reference to build scripts. > > > Yes, that would be fine. So which one? We have: 1. [SourceForge]/mingw/ports/grep/2.5/mingw-patches 2. [SourceForge]/mingw/ports/grep/2.5/patches 3. [SourceForge]/mingw/ports/grep/2.5/build IMO, the first one is redundant. What about the second one? Then the distributed tar ball would be something like: grep-2.5-mingw.tar.gz Tell me what you think, I plan to upload grep2.5 files on Friday. Manu. > > Kees > > > > which > > > contains the patch or patches to the original sources needed to compile > > the > > > package with mingw and the autotools (thus under msys or cygwin). If > > binaries > > > and patched sources would be provided, then these could go into > > subdirectories > > > bin and src, and the compiled docs (chm, htm, pdf) into a subdirectory > > doc. > > > Would this be agreeable? > > > > Yes, very good. > > Manu. > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: See the NEW Palm > > Tungsten T handheld. Power & Color in a compact size! > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > > _______________________________________________ > > MinGW-dvlpr mailing list > > Min...@li... > > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
From: Kees Z. <kz...@us...> - 2002-11-06 22:19:17
|
----- Oorspronkelijk bericht ----- Van: "Manu" <ma...@wa...> Aan: <min...@li...> Verzonden: woensdag 6 november 2002 22:26 Onderwerp: Re: [MinGW-dvlpr] Re: Fw: [Mingw-users] Re: Grep 2.5 for MinGW > Kees Zeelenberg wrote: > > > > ----- Oorspronkelijk bericht ----- > > Van: "Manu" > > Aan: <min...@li...> > > Verzonden: dinsdag 5 november 2002 22:35 > > Onderwerp: Re: [MinGW-dvlpr] Re: Fw: [Mingw-users] Re: Grep 2.5 for MinGW > > > > > > > Kees Zeelenberg wrote: > > > > A suggestion on how to further subdivide the ports subdirectory: It > might > > > be > > > > divided according to package (e.g. grep) and these further divided > > > according > > > > to version numbers (e.g. 2.5). At this second level, in the example > > > > ports/grep/2.25, we might have at least a subdirectory mingw-patches, > > > > > > So we would have 'ports/grep/2.5/mingw-patches'. > > > Or maybe it could be simply ports/grep/2.5/patches > > > or ports/grep/2.5/build > > > in reference to build scripts. > > > > > Yes, that would be fine. > > So which one? > We have: > 1. [SourceForge]/mingw/ports/grep/2.5/mingw-patches > 2. [SourceForge]/mingw/ports/grep/2.5/patches > 3. [SourceForge]/mingw/ports/grep/2.5/build > > IMO, the first one is redundant. > What about the second one? > Then the distributed tar ball would be something like: > grep-2.5-mingw.tar.gz > Tell me what you think, I plan to upload grep2.5 files > on Friday. 2 and/or 3 would be OK with me. Kees > > Manu. > > > > > Kees > > > > > > which > > > > contains the patch or patches to the original sources needed to > compile > > > the > > > > package with mingw and the autotools (thus under msys or cygwin). If > > > binaries > > > > and patched sources would be provided, then these could go into > > > subdirectories > > > > bin and src, and the compiled docs (chm, htm, pdf) into a subdirectory > > > doc. > > > > Would this be agreeable? > > > > > > Yes, very good. > > > Manu. > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by: See the NEW Palm > > > Tungsten T handheld. Power & Color in a compact size! > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > > > _______________________________________________ > > > MinGW-dvlpr mailing list > > > Min...@li... > > > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: See the NEW Palm > > Tungsten T handheld. Power & Color in a compact size! > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > > _______________________________________________ > > MinGW-dvlpr mailing list > > Min...@li... > > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > |
From: F. <j_r...@ya...> - 2002-11-08 14:47:34
|
On Tue, Nov 05, 2002 at 08:01:49AM -0500, Earnie Boyd wrote: > I've added manubee to the list of developers and have associated > ma...@us... with the mingw-dvlpr mailing list. If you > wish to post messages with a different account please let me know. > > Work with Kees on the package layout. The ports subdirectory has > already been added but is empty. I will look at the web pages to decide > what/how w.r.t. promoting MinGW ports. The MinGW ports maintenance, > implementation and distribution belong to you and Kees. I think that this MinGW native ports is a great thing. Unfortunately I no longer have the time or need for such ports, but I once had and spent alot of time and effort in producing the ports available at http://mefriss1.swan.ac.uk/~jfonseca/gnu-win32/software/ported . Although most packages there are now outdated, special care was taken then to deal with the line-endings and other details as explained in the above page. So I think that the diffs of the changes made by me at the time (which were in many cases based on the analysis of the diffs of other ports available then) are still valuable for this effort. So I've put them all on http://mefriss1.swan.ac.uk/~jfonseca/gnu-win32/software/ported/ for your convenience. BTW, the convention taken regarding the line endings was: - read/write hand-written files (configuration files, scripts, etc.) in text mode - read/write raw data files (input/output streams) in binary. Of course that the later is arguable, and probably doesn't make much sense nowadays with the availabilty of MSYS for building unix stuff. It all depends of what you want to do with the ports. José Fonseca __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com |
From: Manu <ma...@wa...> - 2002-11-08 21:38:07
|
Jos=E9 Fonseca wrote: > On Tue, Nov 05, 2002 at 08:01:49AM -0500, Earnie Boyd wrote: > > I've added manubee to the list of developers and have associated > > ma...@us... with the mingw-dvlpr mailing list. If = you > > wish to post messages with a different account please let me know. > > > > Work with Kees on the package layout. The ports subdirectory has > > already been added but is empty. I will look at the web pages to dec= ide > > what/how w.r.t. promoting MinGW ports. The MinGW ports maintenance, > > implementation and distribution belong to you and Kees. > > I think that this MinGW native ports is a great thing. > > Unfortunately I no longer have the time or need for such ports, Who knows.... maybe..... > but I > once had and spent alot of time and effort in producing the ports > available at > http://mefriss1.swan.ac.uk/~jfonseca/gnu-win32/software/ported . > Although most packages there are now outdated, :) I still use some of these nice outdated binaries. > special care was taken > then to deal with the line-endings and other details as explained in > the above page. > > So I think that the diffs of the changes made by me at the time (which > were in many cases based on the analysis of the diffs of other ports > available then) are still valuable for this effort. So I've put them al= l > on http://mefriss1.swan.ac.uk/~jfonseca/gnu-win32/software/ported/ for > your convenience. Great! And much valuable. Thank you. You don't have a lot of time, but I'm glad to see that you still contribu= te to port softwares. It's like a virus isn't it :) > BTW, the convention taken regarding the line endings was: > - read/write hand-written files (configuration files, scripts, etc.) i= n > text mode > - read/write raw data files (input/output streams) in binary. So, CR/LF for hand-written files and LF otherwise? Currently, I've adopted LF-only. I cannot use my home-made Notepad, but my favorite editor (SciTE :) does all the good job. > Of course that the later is arguable, and probably doesn't make much > sense nowadays with the availabilty of MSYS for building unix stuff. It > all depends of what you want to do with the ports. I don't really know what are the pros and the cons. LF-only seems to simplify things, at first glance. Manu. |
From: Earnie B. <ear...@ya...> - 2002-11-08 22:17:20
|
Manu wrote: > > I don't really know what are the pros and the cons. LF-only seems to > simplify things, at first glance. > But may not be what the minimalist Win32 user desires. I prefer it but then should we force it to be? No, I don't think so. Perhaps a CRLF environment variable, with natural default. CRLF=lf #open all files in binary mode including CRT. CRLF=crlf #open all files in text mode regardless of content (default) CRLF=mixed #open files easily created with NotePad in text mode otherwise binary mode. Earnie. P.S.: Exceptions to default would be: unless functionality is totally damaged. |
From: Manu <ma...@wa...> - 2002-11-09 13:19:10
|
Earnie Boyd wrote: > Manu wrote: > > > > I don't really know what are the pros and the cons. LF-only seems to > > simplify things, at first glance. > > > > But may not be what the minimalist Win32 user desires. I prefer it but > then should we force it to be? No, I don't think so. I agree. Currently, ChangeLog, scripts, source files use LF, within MinGW, I took this convention. About GNU-Win32's ported softwares, Jos=E9 Fonseca wrote: > BTW, the convention taken regarding the line endings was: > - read/write hand-written files (configuration files, scripts, etc.) i= n > text mode > - read/write raw data files (input/output streams) in binary. I can convert hand-written files within ports/grep to CRLF, then only the patch would use LF. > Perhaps a CRLF environment variable, with natural default. > > CRLF=3Dlf #open all files in binary mode including CRT. > CRLF=3Dcrlf #open all files in text mode regardless of content (default= ) > CRLF=3Dmixed #open files easily created with NotePad in text mode > otherwise binary mode. Yes, good idea. But how softwares would use this variable? Manu. > Earnie. > P.S.: Exceptions to default would be: unless functionality is totally > damaged. > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |