From: Erwin W. <wat...@xs...> - 2012-02-08 23:10:00
|
Hi, If there is interest I'm willing to package and maintain "dos2unix" for MinGW and MSYS. The version that I maintain is used in major Linux distributions and since Apr 2011 also standard on Cygwin. See http://waterlan.home.xs4all.nl/dos2unix.html On Cygwin it replaced the Cygutils' version of dos2unix. Msys/MinGW also has the Cygutils version. If you don't want it, that's also fine with me. best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-02-10 21:00:41
|
Erwin Waterlander schreef, Op 9-2-2012 0:09: > Hi, > > If there is interest I'm willing to package and maintain "dos2unix" for > MinGW and MSYS. The version that I maintain is used in major Linux > distributions and since Apr 2011 also standard on Cygwin. See > http://waterlan.home.xs4all.nl/dos2unix.html > > On Cygwin it replaced the Cygutils' version of dos2unix. Msys/MinGW also > has the Cygutils version. > > If you don't want it, that's also fine with me. > > best regards, > Hi, I prepared mingw32-dos2unix packages. I put them for review at http://waterlan.home.xs4all.nl/mingw/dos2unix/ regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-02-10 21:46:42
|
Erwin Waterlander schreef, Op 10-2-2012 22:00: > Erwin Waterlander schreef, Op 9-2-2012 0:09: >> Hi, >> >> If there is interest I'm willing to package and maintain "dos2unix" for >> MinGW and MSYS. The version that I maintain is used in major Linux >> distributions and since Apr 2011 also standard on Cygwin. See >> http://waterlan.home.xs4all.nl/dos2unix.html >> >> On Cygwin it replaced the Cygutils' version of dos2unix. Msys/MinGW also >> has the Cygutils version. >> >> If you don't want it, that's also fine with me. >> >> best regards, >> > Hi, > > I prepared mingw32-dos2unix packages. I put them for review at > http://waterlan.home.xs4all.nl/mingw/dos2unix/ > > regards, > I also added msys-dos2unix packages. -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Charles W. <cwi...@us...> - 2012-02-11 10:51:35
|
On 2/8/2012 6:09 PM, Erwin Waterlander wrote: > If there is interest I'm willing to package and maintain "dos2unix" for > MinGW and MSYS. The version that I maintain is used in major Linux > distributions and since Apr 2011 also standard on Cygwin. See > http://waterlan.home.xs4all.nl/dos2unix.html > > On Cygwin it replaced the Cygutils' version of dos2unix. Msys/MinGW also > has the Cygutils version. I'm in favor of this, but we will need to coordinate an update of the existing cygutils packages: msys-cygutils-dos2unix needs to be removed? obsoleted? in favor of the new msys-dos2unix package, with appropriate changes made to msys-base.xml. I'm not sure how this should be handled. Ditto for mingw32-cygutils-dos2unix. Keith -- effectively, this would be a "package rename". How do we handle that? -- Chuck |
From: waterlan <wat...@xs...> - 2012-02-20 14:03:55
|
On 2012-02-11 11:51, Charles Wilson wrote: > On 2/8/2012 6:09 PM, Erwin Waterlander wrote: > >> If there is interest I'm willing to package and maintain "dos2unix" >> for >> MinGW and MSYS. The version that I maintain is used in major Linux >> distributions and since Apr 2011 also standard on Cygwin. See >> http://waterlan.home.xs4all.nl/dos2unix.html [1] On Cygwin it >> replaced >> the Cygutils' version of dos2unix. Msys/MinGW also has the Cygutils >> version. > > I'm in favor of this, but we will need to coordinate an update of the > existing cygutils packages: > > msys-cygutils-dos2unix > > needs to be removed? obsoleted? in favor of the new > > msys-dos2unix > > package, with appropriate changes made to msys-base.xml. I'm not sure > how this should be handled. Ditto for mingw32-cygutils-dos2unix. > > Keith -- effectively, this would be a "package rename". How do we > handle that? > > -- > Chuck Hi Keith, I'm sorry to cc you directly, but I think you missed Chuck's question here. best regards, -- Erwin Waterlander |
From: Keith M. <kei...@us...> - 2012-02-20 23:01:43
|
Erwin, Chuck, Apologies for the delayed response. On 11/02/12 10:51, Charles Wilson wrote: > we will need to coordinate an update of the existing cygutils > packages: > > msys-cygutils-dos2unix > > needs to be removed? obsoleted? in favor of the new > > msys-dos2unix > > package, with appropriate changes made to msys-base.xml. I'm not sure > how this should be handled. Ditto for mingw32-cygutils-dos2unix. > > Keith -- effectively, this would be a "package rename". How do we > handle that? There is no formal mechanism, in mingw-get, to support renaming packages; nor do I have any plans for adding such support. As is the case with CVS, you may rename the package, effectively deleting the old and creating the new, but then there will be no logical relationship between the two. Neither is there, at present, any capability for specifying conflicts between packages, such that if foo is installed, it must be removed on subsequently installing bar. This is a feature I may add eventually, but I don't consider it as an immediate priority. Now, taking mingw32-dos2unix as an example of the present case, what we *can* do right now is derive it from mingw32-cygutils-dos2unix, thus: - change the name attribute of the package defining element, from name="mingw32-cygutils-dos2unix" to name="mingw32-dos2unix" - preserve the relationship to the original cygutils package, by adding the deprecated name(s) to the alias attribute; thus: alias="cygutils-dos2unix" becomes: alias="dos2unix cygutils-dos2unix mingw32-cygutils-dos2unix" - you may also wish to consider further extending the alias list, to include "... mingw32-cygutils cygutils", and coalescing the existing mingw32-cygutils and mingw32-cygutils-dos2unix packages into a single logical mingw32-dos2unix package. - you *will* also want to update the descriptions, to reflect your changes. In this manner, you can effectively rename the package, and preserve the relationship with the original; it's your choice whether you rename the XML file, or not, but if you do, then you will also need to update mingw32-package-list.xml to suit. There is one caveat: your first mingw32-dos2unix package release *must* bear a logically greater version number than the mingw32-cygutils-dos2unix package which it supplants. -- Regards, Keith. |
From: Erwin W. <wat...@xs...> - 2012-02-22 18:59:32
|
Keith Marshall schreef, Op 21-2-2012 0:01: > Erwin, Chuck, > > Apologies for the delayed response. > > On 11/02/12 10:51, Charles Wilson wrote: >> we will need to coordinate an update of the existing cygutils >> packages: >> >> msys-cygutils-dos2unix >> >> needs to be removed? obsoleted? in favor of the new >> >> msys-dos2unix >> >> package, with appropriate changes made to msys-base.xml. I'm not sure >> how this should be handled. Ditto for mingw32-cygutils-dos2unix. >> >> Keith -- effectively, this would be a "package rename". How do we >> handle that? > There is no formal mechanism, in mingw-get, to support renaming > packages; nor do I have any plans for adding such support. As is the > case with CVS, you may rename the package, effectively deleting the old > and creating the new, but then there will be no logical relationship > between the two. > > Neither is there, at present, any capability for specifying conflicts > between packages, such that if foo is installed, it must be removed on > subsequently installing bar. This is a feature I may add eventually, > but I don't consider it as an immediate priority. > > Now, taking mingw32-dos2unix as an example of the present case, what we > *can* do right now is derive it from mingw32-cygutils-dos2unix, thus: > > - change the name attribute of the package defining element, from > > name="mingw32-cygutils-dos2unix" > > to > > name="mingw32-dos2unix" > > - preserve the relationship to the original cygutils package, by adding > the deprecated name(s) to the alias attribute; thus: > > alias="cygutils-dos2unix" > > becomes: > > alias="dos2unix cygutils-dos2unix mingw32-cygutils-dos2unix" > > - you may also wish to consider further extending the alias list, to > include "... mingw32-cygutils cygutils", and coalescing the existing > mingw32-cygutils and mingw32-cygutils-dos2unix packages into a single > logical mingw32-dos2unix package. > > - you *will* also want to update the descriptions, to reflect your > changes. > > In this manner, you can effectively rename the package, and preserve the > relationship with the original; it's your choice whether you rename the > XML file, or not, but if you do, then you will also need to update > mingw32-package-list.xml to suit. There is one caveat: your first > mingw32-dos2unix package release *must* bear a logically greater version > number than the mingw32-cygutils-dos2unix package which > it supplants. > Hi, The current mingw-cygutils-dos2unix package has one alias "mingw-dos2unix". The name of the new package is "mingw-dos2unix". It has no relation with cygutils. But if you don't want to disappoint people who type 'mingw-get install mingw-cygutils-dos2unix', I can add alias="mingw-cygutils-dos2unix" to the xml file. The version of the new package is 5.3.2, which is higher than the version of mingw-cygutils-dos2unix (1.3.4). This should work, isn't it? Where should I upload the new files? The current cygutils-dos2unix package resides under 'Extension'. Should I put them under Extension/dos2unix/5.3.2/. Or, because it's a contributed package,under Contributed/dos2unix/5.3.2/ best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Keith M. <kei...@us...> - 2012-02-22 22:29:24
|
On 22/02/12 18:59, Erwin Waterlander wrote: > The current mingw-cygutils-dos2unix package ... The current package is called "mingw32-cygutil-dos2unix"; I assume your "mingw-..." is an accidental omission, but just in case, you need to s/mingw/mingw32/g in all instances please. > ... has one alias "mingw-dos2unix". That's not what I see: <package name="mingw32-cygutils-dos2unix" alias="cygutils-dos2unix"> > The name of the new package is "mingw-dos2unix". That needs to be "mingw32-dos2unix", so you may rewrite the header as: <package name="mingw32-dos2unix" alias="dos2unix cygutils-dos2unix mingw32-cygutils-dos2unix"> (You are allowed only one "alias" attribute, but it may specify multiple aliases, separated by spaces). > It has no relation with cygutils. It has, in the sense that it (presumably) provides replacements for the cygutils payload, e.g. dos2unix.exe, unix2dos.exe ... > But if you don't want to disappoint > people who type 'mingw-get install mingw-cygutils-dos2unix', This isn't the issue; you *must* preserve a relationship, to ensure that when your package is installed, the payload from any previously installed mingw32-cygutils-dos2unix is properly removed. If you don't do this, then you violate project policy by introducing two distinct packages which deliver conflicting payloads. > I can add alias="mingw-cygutils-dos2unix" to the xml file. As I've shown it above, please: "mingw32-cygutils-dos2unix". > The version of the new package is 5.3.2, which is higher than the > version of mingw-cygutils-dos2unix (1.3.4). This should work, isn't > it? Yes. > Where should I upload the new files? The current cygutils-dos2unix > package resides under 'Extension'. Should I put them under > Extension/dos2unix/5.3.2/. Or, because it's a contributed package,under > Contributed/dos2unix/5.3.2/ Keeping it as an "extension" package seems best to me. -- Regards, Keith. |
From: Charles W. <cwi...@us...> - 2012-02-23 00:07:33
|
On 2/22/2012 5:29 PM, Keith Marshall wrote: > Keeping it as an "extension" package seems best to me. Agreed. -- Chuck |
From: Erwin W. <wat...@xs...> - 2012-02-24 09:23:19
|
Op 21-2-2012 0:01, Keith Marshall schreef: > Erwin, Chuck, > > Apologies for the delayed response. > > On 11/02/12 10:51, Charles Wilson wrote: >> we will need to coordinate an update of the existing cygutils >> packages: >> >> msys-cygutils-dos2unix >> >> needs to be removed? obsoleted? in favor of the new >> >> msys-dos2unix >> >> package, with appropriate changes made to msys-base.xml. I'm not sure >> how this should be handled. Ditto for mingw32-cygutils-dos2unix. >> >> Keith -- effectively, this would be a "package rename". How do we >> handle that? > There is no formal mechanism, in mingw-get, to support renaming > packages; nor do I have any plans for adding such support. As is the > case with CVS, you may rename the package, effectively deleting the old > and creating the new, but then there will be no logical relationship > between the two. > > Neither is there, at present, any capability for specifying conflicts > between packages, such that if foo is installed, it must be removed on > subsequently installing bar. This is a feature I may add eventually, > but I don't consider it as an immediate priority. > > Now, taking mingw32-dos2unix as an example of the present case, what we > *can* do right now is derive it from mingw32-cygutils-dos2unix, thus: > > - change the name attribute of the package defining element, from > > name="mingw32-cygutils-dos2unix" > > to > > name="mingw32-dos2unix" > > - preserve the relationship to the original cygutils package, by adding > the deprecated name(s) to the alias attribute; thus: > > alias="cygutils-dos2unix" > > becomes: > > alias="dos2unix cygutils-dos2unix mingw32-cygutils-dos2unix" > > - you may also wish to consider further extending the alias list, to > include "... mingw32-cygutils cygutils", and coalescing the existing > mingw32-cygutils and mingw32-cygutils-dos2unix packages into a single > logical mingw32-dos2unix package. > > - you *will* also want to update the descriptions, to reflect your > changes. > > In this manner, you can effectively rename the package, and preserve the > relationship with the original; it's your choice whether you rename the > XML file, or not, but if you do, then you will also need to update > mingw32-package-list.xml to suit. There is one caveat: your first > mingw32-dos2unix package release *must* bear a logically greater version > number than the mingw32-cygutils-dos2unix package which > it supplants. > The new mingw32-dos2unix and msys-dos2unix have their own xml file (not uploaded yet). msys-dos2unix: <package name="msys-dos2unix" alias="msys-cygutils-dos2unix"> mingw32-dos2unix: <package name="mingw32-dos2unix" alias="mingw32-cygutils-dos2unix cygutils-dos2unix dos2unix unix2dos"> As I understand it, the following should now be done: 1) Charles should remove the dos2unix package sections from the cygutils xml files 2) The new dos2unix xml files have to be uploaded 3) The package lists should be updated with an addition of the new dos2unix packages. Is this correct? -- Erwin |
From: Erwin W. <wat...@xs...> - 2012-02-28 19:57:26
|
Erwin Waterlander schreef, Op 24-2-2012 10:23: > Op 21-2-2012 0:01, Keith Marshall schreef: >> Erwin, Chuck, >> >> Apologies for the delayed response. >> >> On 11/02/12 10:51, Charles Wilson wrote: >>> we will need to coordinate an update of the existing cygutils >>> packages: >>> >>> msys-cygutils-dos2unix >>> >>> needs to be removed? obsoleted? in favor of the new >>> >>> msys-dos2unix >>> >>> package, with appropriate changes made to msys-base.xml. I'm not sure >>> how this should be handled. Ditto for mingw32-cygutils-dos2unix. >>> >>> Keith -- effectively, this would be a "package rename". How do we >>> handle that? >> There is no formal mechanism, in mingw-get, to support renaming >> packages; nor do I have any plans for adding such support. As is the >> case with CVS, you may rename the package, effectively deleting the old >> and creating the new, but then there will be no logical relationship >> between the two. >> >> Neither is there, at present, any capability for specifying conflicts >> between packages, such that if foo is installed, it must be removed on >> subsequently installing bar. This is a feature I may add eventually, >> but I don't consider it as an immediate priority. >> >> Now, taking mingw32-dos2unix as an example of the present case, what we >> *can* do right now is derive it from mingw32-cygutils-dos2unix, thus: >> >> - change the name attribute of the package defining element, from >> >> name="mingw32-cygutils-dos2unix" >> >> to >> >> name="mingw32-dos2unix" >> >> - preserve the relationship to the original cygutils package, by adding >> the deprecated name(s) to the alias attribute; thus: >> >> alias="cygutils-dos2unix" >> >> becomes: >> >> alias="dos2unix cygutils-dos2unix mingw32-cygutils-dos2unix" >> >> - you may also wish to consider further extending the alias list, to >> include "... mingw32-cygutils cygutils", and coalescing the existing >> mingw32-cygutils and mingw32-cygutils-dos2unix packages into a single >> logical mingw32-dos2unix package. >> >> - you *will* also want to update the descriptions, to reflect your >> changes. >> >> In this manner, you can effectively rename the package, and preserve the >> relationship with the original; it's your choice whether you rename the >> XML file, or not, but if you do, then you will also need to update >> mingw32-package-list.xml to suit. There is one caveat: your first >> mingw32-dos2unix package release *must* bear a logically greater version >> number than the mingw32-cygutils-dos2unix package which >> it supplants. >> > The new mingw32-dos2unix and msys-dos2unix have their own xml file (not > uploaded yet). > msys-dos2unix: > <package name="msys-dos2unix" alias="msys-cygutils-dos2unix"> > mingw32-dos2unix: > <package name="mingw32-dos2unix" alias="mingw32-cygutils-dos2unix > cygutils-dos2unix dos2unix unix2dos"> > > As I understand it, the following should now be done: > > 1) Charles should remove the dos2unix package sections from the cygutils > xml files > 2) The new dos2unix xml files have to be uploaded > 3) The package lists should be updated with an addition of the new > dos2unix packages. > > Is this correct? > If I don't hear anything this week I assume it is OK. I change the xml files next week. best regards, -- Erwin Waterlander |
From: Keith M. <kei...@us...> - 2012-03-01 22:34:46
|
On 28/02/12 19:57, Erwin Waterlander wrote: >> As I understand it, the following should now be done: >> >> 1) Charles should remove the dos2unix package sections from the >> cygutils xml files And the history for those components needs to be encapsulated in your replacement files. >> 2) The new dos2unix xml files have to be uploaded >> 3) The package lists should be updated with an addition of the >> new dos2unix packages. >> >> Is this correct? Since these will be officially supported packages, your changes must be properly integrated into mingw-dist; there is a little bit more to this than simply uploading a new xml file or two. > If I don't hear anything this week I assume it is OK. I change the > xml files next week. Please hold off on this... At a cursory glance, I note that you haven't set the issue number appropriately, in the <software-distribution .../> elements of your xml files. Aside from this, and the missing history from the cygutils components you are superseding, they look superficially okay; however, we do need to thoroughly test the intended interactions, before we consider uploading any new xml files; my own preliminary testing suggests that this may not work, so we may need a rethink. -- Regards, Keith. |
From: Erwin W. <wat...@xs...> - 2012-03-02 10:37:46
|
Op 1-3-2012 23:34, Keith Marshall schreef: > On 28/02/12 19:57, Erwin Waterlander wrote: >>> As I understand it, the following should now be done: >>> >>> 1) Charles should remove the dos2unix package sections from the >>> cygutils xml files > And the history for those components needs to be encapsulated in your > replacement files. I don't understand what that means. I have added the cygutils aliases. What else do I need to do? Perhaps a paragraph in the release notes that says, that the package replaces cygutils-dos2unix? > >>> 2) The new dos2unix xml files have to be uploaded >>> 3) The package lists should be updated with an addition of the >>> new dos2unix packages. >>> >>> Is this correct? > Since these will be officially supported packages, your changes must > be properly integrated into mingw-dist; there is a little bit more to > this than simply uploading a new xml file or two. > >> If I don't hear anything this week I assume it is OK. I change the >> xml files next week. > Please hold off on this... > > At a cursory glance, I note that you haven't set the issue number > appropriately, in the<software-distribution .../> elements of your I will fix that. > xml files. Aside from this, and the missing history from the cygutils > components you are superseding, they look superficially okay; however, > we do need to thoroughly test the intended interactions, before we > consider uploading any new xml files; my own preliminary testing > suggests that this may not work, so we may need a rethink. > I agree. -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Keith M. <kei...@us...> - 2012-03-03 11:37:22
|
On 02/03/12 10:37, Erwin Waterlander wrote: >>> 1) Charles should remove the dos2unix package sections from the >>> cygutils xml files >> >> And the history for those components needs to be encapsulated in your >> replacement files. > > I don't understand what that means. I have added the cygutils aliases. > What else do I need to do? You want to provide an upgrade path, such that mingw-get will view any prior installation of cygutils-dos2unix as upgradeable to your dos2unix replacement. It can't make this association automatically, because the tarname of your new package doesn't match the tarname of the old, as it is recorded in the sysroot-*.xml files, so you need to tell it. You do this by including release references for the old package, within the component specification for the new, e.g.:-- <component class="bin"> <release tarname="dos2unix-5.3.2-1-mingw32-bin.tar.lzma"> <requires eq="mingw32-libiconv-*-mingw32-*-dll-2.tar" /> <requires eq="mingw32-libintl-*-mingw32-*-dll-8.tar" /> </release> <release tarname="cygutils-dos2unix-1.3.4-1-mingw32-bin.tar.lzma"> <licence tarname="cygutils-%-mingw32-%-lic.tar.%" /> <source tarname="cygutils-%-mingw32-%-src.tar.%" /> <requires eq="mingw32-libpopt-*-mingw32-*-dll-0.tar" /> </release> </component> > Perhaps a paragraph in the release notes that says, that the package > replaces cygutils-dos2unix? That isn't sufficient; mingw-get can't read your release notes. -- Regards, Keith. |
From: Erwin W. <wat...@xs...> - 2012-03-04 20:38:18
|
Keith Marshall schreef, Op 3-3-2012 12:37:Keith Marshall schreef, Op 3-3-2012 12:37: > You want to provide an upgrade path, such that mingw-get will view any > prior installation of cygutils-dos2unix as upgradeable to your dos2unix > replacement. It can't make this association automatically, because the > tarname of your new package doesn't match the tarname of the old, as it > is recorded in the sysroot-*.xml files, so you need to tell it. You do > this by including release references for the old package, within the > component specification for the new, e.g.:-- > > <component class="bin"> > <release tarname="dos2unix-5.3.2-1-mingw32-bin.tar.lzma"> > <requires eq="mingw32-libiconv-*-mingw32-*-dll-2.tar" /> > <requires eq="mingw32-libintl-*-mingw32-*-dll-8.tar" /> > </release> > <release tarname="cygutils-dos2unix-1.3.4-1-mingw32-bin.tar.lzma"> > <licence tarname="cygutils-%-mingw32-%-lic.tar.%" /> > <source tarname="cygutils-%-mingw32-%-src.tar.%" /> > <requires eq="mingw32-libpopt-*-mingw32-*-dll-0.tar" /> > </release> > </component> > > Hi Keith, Thanks. I added that to the xml files. Do I need to do this only for component class "bin"? What are the next steps? regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-03-13 16:49:21
|
On 2012-03-04 21:37, Erwin Waterlander wrote: > Keith Marshall schreef, Op 3-3-2012 12:37:Keith Marshall schreef, Op > 3-3-2012 12:37: > >> You want to provide an upgrade path, such that mingw-get will view >> any >> prior installation of cygutils-dos2unix as upgradeable to your >> dos2unix >> replacement. It can't make this association automatically, because >> the >> tarname of your new package doesn't match the tarname of the old, as >> it >> is recorded in the sysroot-*.xml files, so you need to tell it. You >> do >> this by including release references for the old package, within the >> component specification for the new, e.g.:-- > > Hi Keith, > > Thanks. I added that to the xml files. Do I need to do this only for > component class "bin"? > What are the next steps? > > Hi Keith, Are the xml files correct now? Do the cygutils xml files need to be edited? How can it be tested without messing up the official xml catalogue? Can I do the testing? -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Keith M. <kei...@us...> - 2012-03-30 20:21:24
|
Hi Erwin, Sorry for the delayed response; I've been busy with other issues. On 13/03/12 16:49, Erwin Waterlander wrote: >> Thanks. I added that to the xml files. Okay, thanks. >> Do I need to do this only for component class "bin"? If you want your own documentation and/or licence files to supplant the corresponding files from cygutils, then you also need to update their component specifications accordingly. It seems to me, particularly in the case of the mingw32-cygutils package, that you could/should adopt everything, and allow that original package to disappear, but I'd like to have Chuck's opinion before just jumping in. >> What are the next steps? Replace the issue attributes in your current files with a generic issue template, of the form @YYYYMMDDNN@, and integrate them into mingw-dist. I guess it would make sense for me to grant you CVS access, if you are happy to manage that yourself? > Are the xml files correct now? They look very close to it, AFAICS. I'd rather hoped that Chuck might have chimed in though, since you are supplanting his packages. > Do the cygutils xml files need to be edited? Yes. References for the components you are supplanting need to be removed, since your new dos2unix.xml will take "ownership" of them. > How can it be tested without messing up the official xml catalogue? For local testing, you can simply modify the (uncompressed) copies in your local $MINGW_GET_ROOT/var/lib/mingw-get/data directory, and run various mingw-get commands, to confirm correct behaviour. If you'd like an example of how to set up a mingw-get sandbox, take a look at https://sourceforge.net/tracker/?func=detail&atid=102435&aid=3424406&group_id=2435 > Can I do the testing? Sure. Confirm that you can 'mingw-get upgrade ...' from an existing cygutils installation, with proper substitution of your own components, and that 'mingw-get show mingw32-dos2unix-bin' (for example), reflects the correct package status, (particularly the 'Installed Version' and 'Repository Version' notifications), when you run it both before and after the 'mingw-get upgrade ...', and post your results here. -- Regards, Keith. |
From: Charles W. <cwi...@us...> - 2012-03-30 21:51:03
|
On 3/30/2012 8:59 AM, Keith Marshall wrote: > Hi Erwin, > > Sorry for the delayed response; I've been busy with other issues. > > On 13/03/12 16:49, Erwin Waterlander wrote: >>> Thanks. I added that to the xml files. > > Okay, thanks. > >>> Do I need to do this only for component class "bin"? > > If you want your own documentation and/or licence files to supplant the > corresponding files from cygutils, then you also need to update their > component specifications accordingly. It seems to me, particularly in > the case of the mingw32-cygutils package, that you could/should adopt > everything, and allow that original package to disappear, but I'd like > to have Chuck's opinion before just jumping in. Yes, this is the right thing to do. >>> What are the next steps? > > Replace the issue attributes in your current files with a generic issue > template, of the form @YYYYMMDDNN@, and integrate them into mingw-dist. > I guess it would make sense for me to grant you CVS access, if you are > happy to manage that yourself? > >> Are the xml files correct now? > > They look very close to it, AFAICS. I'd rather hoped that Chuck might > have chimed in though, since you are supplanting his packages. Sorry, I didn't realize my input was needed. I'll take a look tonight. I'll reply to the rest of this message at that time. -- Chuck |
From: Charles W. <cwi...@us...> - 2012-04-02 01:23:39
Attachments:
cygutils-xml-update.patch
msys-base-update.patch
|
On 3/30/2012 8:59 AM, Keith Marshall wrote: > If you want your own documentation and/or licence files to supplant the > corresponding files from cygutils, then you also need to update their > component specifications accordingly. It seems to me, particularly in > the case of the mingw32-cygutils package, that you could/should adopt > everything, and allow that original package to disappear, but I'd like > to have Chuck's opinion before just jumping in. I think the existing *-cygutils.xml files should be updated as in the attached patch, which removes all mention of *-cygutils-dos2unix ... thus letting the new *-dos2unix.xml files "take over". Also, as msys-cygutils-dos2unix WAS part of <affiliate group="MSYS Base System" /> I believe that the new msys-dos2unix should ALSO be a part of that. Similarly, msys-base.xml should be updated as attached (although the alias in the new msys-dos2unix package means that msys-base doesn't NEED to be changed, it's better to be explicit and not rely on the alias). >>> What are the next steps? > > Replace the issue attributes in your current files with a generic issue > template, of the form @YYYYMMDDNN@, and integrate them into mingw-dist. > I guess it would make sense for me to grant you CVS access, if you are > happy to manage that yourself? > >> Are the xml files correct now? > > They look very close to it, AFAICS. I'd rather hoped that Chuck might > have chimed in though, since you are supplanting his packages. Actually, if we are convinced that things are copacetic (with the attached patches and the above-mentioned changes to the new xml files), I don't mind doing the initial mingw-dist integration; we can then leave the mingw-dist *updated* to Erwin when/as he releases new versions in the future. Basically, it boils down to adding the new files to the appropriate package list xml: msys/msys-package-list.xml mingw32/mingw32-package-list.xml ...and adding a changeLog entry. (After building, the */issue.log files will be modified automatically, and those changes should be checked in. But that should only be done once, by the final committer for that change.) However, it would be great if... >> Do the cygutils xml files need to be edited? > > Yes. References for the components you are supplanting need to be > removed, since your new dos2unix.xml will take "ownership" of them. See attached patches. >> Can I do the testing? > > Sure. Confirm that you can 'mingw-get upgrade ...' from an existing > cygutils installation, with proper substitution of your own components, > and that 'mingw-get show mingw32-dos2unix-bin' (for example), reflects > the correct package status, (particularly the 'Installed Version' and > 'Repository Version' notifications), when you run it both before and > after the 'mingw-get upgrade ...', and post your results here. ...Erwin could verify this first. -- Chuck |
From: Erwin W. <wat...@xs...> - 2012-04-03 19:10:06
|
Charles Wilson schreef, Op 2-4-2012 3:23: > On 3/30/2012 8:59 AM, Keith Marshall wrote: >> If you want your own documentation and/or licence files to supplant the >> corresponding files from cygutils, then you also need to update their >> component specifications accordingly. It seems to me, particularly in >> the case of the mingw32-cygutils package, that you could/should adopt >> everything, and allow that original package to disappear, but I'd like >> to have Chuck's opinion before just jumping in. > > I think the existing *-cygutils.xml files should be updated as in the > attached patch, which removes all mention of *-cygutils-dos2unix ... > thus letting the new *-dos2unix.xml files "take over". > > Also, as msys-cygutils-dos2unix WAS part of > <affiliate group="MSYS Base System" /> I have added this to msys-dos2unix.xml > I believe that the new msys-dos2unix should ALSO be a part of that. > Similarly, msys-base.xml should be updated as attached (although the > alias in the new msys-dos2unix package means that msys-base doesn't > NEED to be changed, it's better to be explicit and not rely on the > alias). > >>>> What are the next steps? >> >> Replace the issue attributes in your current files with a generic issue >> template, of the form @YYYYMMDDNN@, and integrate them into mingw-dist. >> I guess it would make sense for me to grant you CVS access, if you are >> happy to manage that yourself? >> >>> Are the xml files correct now? >> >> They look very close to it, AFAICS. I'd rather hoped that Chuck might >> have chimed in though, since you are supplanting his packages. > > Actually, if we are convinced that things are copacetic (with the > attached patches and the above-mentioned changes to the new xml > files), I don't mind doing the initial mingw-dist integration; we can > then leave the mingw-dist *updated* to Erwin when/as he releases new > versions in the future. That's fine with me. > > Basically, it boils down to adding the new files to the appropriate > package list xml: > > msys/msys-package-list.xml > mingw32/mingw32-package-list.xml > > ...and adding a changeLog entry. (After building, the */issue.log > files will be modified automatically, and those changes should be > checked in. But that should only be done once, by the final committer > for that change.) > > However, it would be great if... > >>> Do the cygutils xml files need to be edited? >> >> Yes. References for the components you are supplanting need to be >> removed, since your new dos2unix.xml will take "ownership" of them. > > See attached patches. > >>> Can I do the testing? >> >> Sure. Confirm that you can 'mingw-get upgrade ...' from an existing >> cygutils installation, with proper substitution of your own components, >> and that 'mingw-get show mingw32-dos2unix-bin' (for example), reflects >> the correct package status, (particularly the 'Installed Version' and >> 'Repository Version' notifications), when you run it both before and >> after the 'mingw-get upgrade ...', and post your results here. > > ...Erwin could verify this first. I will do this. It may take some time. I have to confess I never used mingw-get until now. I still did manual install... best regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-04-03 18:54:36
|
Keith Marshall schreef, Op 30-3-2012 14:59: > Hi Erwin, > > Sorry for the delayed response; I've been busy with other issues. No problem. In the meantime I released a new dos2unix version 5.3.3. >>> Do I need to do this only for component class "bin"? > If you want your own documentation and/or licence files to supplant the > corresponding files from cygutils, then you also need to update their > component specifications accordingly. It seems to me, particularly in > the case of the mingw32-cygutils package, that you could/should adopt The idea is to only replace the mingw32-cygutils-dos2unix package and keep the ming32-cygutils package, and likewise for the msys variant. The mingw32-cygutils-dos2unix package has no 'doc' and 'lic' component. The source and license files are already specified in my xml files. So I think I can keep the xml files as they are. > everything, and allow that original package to disappear, but I'd like > to have Chuck's opinion before just jumping in. Me too. >> How can it be tested without messing up the official xml catalogue? > For local testing, you can simply modify the (uncompressed) copies in > your local $MINGW_GET_ROOT/var/lib/mingw-get/data directory, and run > various mingw-get commands, to confirm correct behaviour. If you'd like > an example of how to set up a mingw-get sandbox, take a look at > https://sourceforge.net/tracker/?func=detail&atid=102435&aid=3424406&group_id=2435 I will have look. > >> Can I do the testing? > Sure. Confirm that you can 'mingw-get upgrade ...' from an existing > cygutils installation, with proper substitution of your own components, > and that 'mingw-get show mingw32-dos2unix-bin' (for example), reflects > the correct package status, (particularly the 'Installed Version' and > 'Repository Version' notifications), when you run it both before and > after the 'mingw-get upgrade ...', and post your results here. > Okay, I will try. -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-04-03 20:15:53
|
Charles Wilson schreef, Op 2-4-2012 3:23: > >> Sure. Confirm that you can 'mingw-get upgrade ...' from an existing >> cygutils installation, with proper substitution of your own components, >> and that 'mingw-get show mingw32-dos2unix-bin' (for example), reflects >> the correct package status, (particularly the 'Installed Version' and >> 'Repository Version' notifications), when you run it both before and >> after the 'mingw-get upgrade ...', and post your results here. > > > ...Erwin could verify this first. Hi, I did the following: I moved my original c:\mingw folder away and created a new one. I installed mingw-get under c:/mingw and changed PATH=c:\mingw\bin;%PATH% I ran "mingw-get install mingw32-cygutils-dos2unix". This installed the requested package and the required packages. Xml files have been downloaded under var/lib/mingw-get/data/. I applied Charles' two patches, and I added my new mingw32-dos2unix.xml and msys-dos2unix.xml to the data directory. When I try to install mingw32-dos2unix I get the message that the package is unknown. What did I forget? c:\mingw>find . -name mingw32-dos2unix.xml .\var\lib\mingw-get\data\mingw32-dos2unix.xml c:\mingw>set MINGW_GET_ROOT=c:/mingw c:\mingw>mingw-get install mingw32-dos2unix mingw-get: *** WARNING *** c:\mingw\var/lib/mingw-get/data/profile.xml: user configuration file missing mingw-get: *** INFO *** c:\mingw\var/lib/mingw-get/data/defaults.xml: trying system default configuration mingw-get: *** ERROR *** mingw32-dos2unix: unknown package c:\mingw> -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Erwin W. <wat...@xs...> - 2012-04-03 20:31:23
|
Erwin Waterlander schreef, Op 3-4-2012 22:15: > Charles Wilson schreef, Op 2-4-2012 3:23: >>> Sure. Confirm that you can 'mingw-get upgrade ...' from an existing >>> cygutils installation, with proper substitution of your own components, >>> and that 'mingw-get show mingw32-dos2unix-bin' (for example), reflects >>> the correct package status, (particularly the 'Installed Version' and >>> 'Repository Version' notifications), when you run it both before and >>> after the 'mingw-get upgrade ...', and post your results here. >> >> ...Erwin could verify this first. > Hi, > > I did the following: I moved my original c:\mingw folder away and > created a new one. I installed mingw-get under c:/mingw and changed > PATH=c:\mingw\bin;%PATH% > I ran "mingw-get install mingw32-cygutils-dos2unix". This installed the > requested package and the required packages. Xml files have been > downloaded under var/lib/mingw-get/data/. > > I applied Charles' two patches, and I added my new mingw32-dos2unix.xml > and msys-dos2unix.xml to the data directory. When I try to install > mingw32-dos2unix I get the message that the package is unknown. What did > I forget? > I forget to add msys-dos2unix and mingw32-dos2unix to the package lists. After adding them installation was successful: c:\mingw>mingw-get install mingw32-cygutils-dos2unix mingw-get: *** WARNING *** c:\mingw\var/lib/mingw-get/data/profile.xml: user configuration file missing mingw-get: *** INFO *** c:\mingw\var/lib/mingw-get/data/defaults.xml: trying system default configuration http://prdownloads.sourceforge.net/mingw/dos2unix-5.3.3-1-mingw32-bin.tar.lzma?download 18.47 kB / 18.47 kB |================================================| 100% http://prdownloads.sourceforge.net/mingw/dos2unix-5.3.3-1-mingw32-doc.tar.lzma?download 32.42 kB / 32.42 kB |================================================| 100% http://prdownloads.sourceforge.net/mingw/dos2unix-5.3.3-1-mingw32-lic.tar.lzma?download 992 B / 992 B |================================================| 100% upgrade: dos2unix-5.3.3-1-mingw32-bin.tar.lzma removing release cygutils-dos2unix-1.3.4-1-mingw32-bin.tar.lzma installing dos2unix-5.3.3-1-mingw32-bin.tar.lzma install: dos2unix-5.3.3-1-mingw32-doc.tar.lzma installing dos2unix-5.3.3-1-mingw32-doc.tar.lzma install: dos2unix-5.3.3-1-mingw32-lic.tar.lzma installing dos2unix-5.3.3-1-mingw32-lic.tar.lzma c:\mingw>dos2unix -V dos2unix 5.3.3 (2012-03-10) Met moedertaal ondersteuning. Windows 32 bit versie (MinGW). LOCALEDIR: c:/mingw/share/locale c:\mingw>mingw-get install msys-cygutils-dos2unix mingw-get: *** WARNING *** c:\mingw\var/lib/mingw-get/data/profile.xml: user configuration file missing mingw-get: *** INFO *** c:\mingw\var/lib/mingw-get/data/defaults.xml: trying system default configuration http://prdownloads.sourceforge.net/mingw/dos2unix-5.3.3-1-msys-1.0.17-bin.tar.lzma?download 17.25 kB / 17.25 kB |================================================| 100% http://prdownloads.sourceforge.net/mingw/dos2unix-5.3.3-1-msys-1.0.17-doc.tar.lzma?download 33.15 kB / 33.15 kB |================================================| 100% http://prdownloads.sourceforge.net/mingw/dos2unix-5.3.3-1-msys-1.0.17-lic.tar.lzma?download 992 B / 992 B |================================================| 100% upgrade: dos2unix-5.3.3-1-msys-1.0.17-bin.tar.lzma removing release cygutils-dos2unix-1.3.4-4-msys-1.0.13-bin.tar.lzma installing dos2unix-5.3.3-1-msys-1.0.17-bin.tar.lzma install: dos2unix-5.3.3-1-msys-1.0.17-doc.tar.lzma installing dos2unix-5.3.3-1-msys-1.0.17-doc.tar.lzma install: dos2unix-5.3.3-1-msys-1.0.17-lic.tar.lzma installing dos2unix-5.3.3-1-msys-1.0.17-lic.tar.lzma regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |
From: Keith M. <kei...@us...> - 2012-04-03 20:34:52
|
On 03/04/12 21:15, Erwin Waterlander wrote: > I applied Charles' two patches, and I added my new mingw32-dos2unix.xml > and msys-dos2unix.xml to the data directory. When I try to install > mingw32-dos2unix I get the message that the package is unknown. What did > I forget? I guess you're missing a reference in mingw32-package-list.xml, to tell mingw-get to read your new file. Ditto for msys-package-list.xml -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2012-04-03 20:25:17
|
On 03/04/12 19:54, Erwin Waterlander wrote: > The idea is to only replace the mingw32-cygutils-dos2unix package and > keep the ming32-cygutils package, and likewise for the msys variant. The > mingw32-cygutils-dos2unix package has no 'doc' and 'lic' component. The 'doc' and 'lic' components are furnished by mingw32-cygutils. AFAICS, beyond providing this documentation, together with additional documentation for other utilities which are not provided, once the mingw32-cygutils-dos2unix is deprecated, mingw32-cygutils ceases to provide anything useful; both need to die together. > The source and license files are already specified in my xml files. > So I think I can keep the xml files as they are. See above. Your dos2unix package provides its own documentation and licence components. These deprecate the corresponding mingw32-cygutils equivalents; your XML needs to reflect this. -- Regards, Keith. |