headers
Earnie Boyd | 1 Apr 2012 16:16
Picon

Re: mingw-get: [RFC] forcing a particular package version

On Fri, Mar 30, 2012 at 11:34 AM, Keith Marshall
<keithmarshall <at> users.sourceforge.net> wrote:
> Guys,
>
> I've been experimenting with a code modification, to allow users to
> force installation of a specific version, other than the most recently
> released version, of any package; for example
>
>  $ mingw-get install "gcc=4.5.*"
>
> would install the latest gcc-4.5.x release, eschewing gcc-4.6.x
>
> I already have this (mostly) working.  However while the above example
> does work, the wild card is needed:
>
>  $ mingw-get install "gcc=4.5"
>
> doesn't work, (because there is no release with a version number which
> is an *exact* match for gcc-4.5-mingw32-...); it currently fails with:
>
>  mingw-get: *** ERROR *** internal package specification error
>  mingw-get: *** ERROR *** can't get 'tarname' for non-release element \
>     <<<unknown>>>
>  mingw-get: *** ERROR *** please report this to the package maintainer
>
> which isn't particularly helpful; it arises because, although the named
> package was found, no suitable release was selected, and an install was
> scheduled with a NULL pointer to the release record: hence, no tarname
> attribute retrievable via that NULL pointer.  I'll need to devise some
> more elegant handling for this condition, before releasing.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Charles Wilson | 2 Apr 2012 03:23
Picon

Re: dos2unix

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  <at> YYYYMMDDNN <at> , 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.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Charles Wilson | 2 Apr 2012 03:46
Picon

Re: mingw-get: [RFC] forcing a particular package version

On 3/30/2012 11:34 AM, Keith Marshall wrote:
> I've been experimenting with a code modification, to allow users to
> force installation of a specific version,

<Monty Burns>Excellent</>

> However while the above example
> does work, the wild card is needed:
>
>    $ mingw-get install "gcc=4.5"
>
> doesn't work, (because there is no release with a version number which
> is an *exact* match for gcc-4.5-mingw32-...); it currently fails with:
>
>    mingw-get: *** ERROR *** internal package specification error
>    mingw-get: *** ERROR *** can't get 'tarname' for non-release element \
>       <<<unknown>>>
>    mingw-get: *** ERROR *** please report this to the package maintainer
>
> which isn't particularly helpful;

> Now, we have a choice here.  Should we accept that the user is required
> to specify the wild card?  Or should mingw-get append it automatically?
> I'm undecided.  Requiring it gives users more explicit control; adding
> it automatically may seem more user friendly, (and either
>
>    $ mingw-get install "gcc=4.5.*"
>
>    $ mingw-get install "gcc=4.5.2-1"
>
(Continue reading)

Permalink | Reply | 3 comments |
headers
Erwin Waterlander | 3 Apr 2012 20:54
Picon
Picon
Favicon

Re: dos2unix

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
(Continue reading)

Permalink | Reply | 23 comments |
headers
Erwin Waterlander | 3 Apr 2012 21:09
Picon
Picon
Favicon

Re: dos2unix

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  <at> YYYYMMDDNN <at> , 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?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Erwin Waterlander | 3 Apr 2012 22:15
Picon
Picon
Favicon

Re: dos2unix

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
(Continue reading)

Permalink | Reply | 2 comments |
headers
Keith Marshall | 3 Apr 2012 22:25
Picon

Re: dos2unix

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.

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
Permalink | Reply | 22 comments |
headers
Erwin Waterlander | 3 Apr 2012 22:31
Picon
Picon
Favicon

Re: dos2unix

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:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Keith Marshall | 3 Apr 2012 22:34
Picon

Re: dos2unix

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.

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
Permalink | Reply | 0 comments |
headers
Erwin Waterlander | 3 Apr 2012 22:56
Picon
Picon
Favicon

Re: dos2unix

Keith Marshall schreef, Op 3-4-2012 22:25:
> 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.

You are right.

>
>> 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.
>

OK. I updated the mingw32-dos2unix.xml file. After adding the 
mingw32-cygutils old doc and lic packages, you can see that the doc and 
lic packages get updated:

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
(Continue reading)

Permalink | Reply | 0 comments |

Gmane