public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS]  can't get ecosconfig to use "current" version
@ 2007-05-22 14:39 Grant Edwards
  2007-05-22 16:27 ` [ECOS] " Grant Edwards
  2007-05-22 20:06 ` Grant Edwards
  0 siblings, 2 replies; 3+ messages in thread
From: Grant Edwards @ 2007-05-22 14:39 UTC (permalink / raw)
  To: ecos-discuss

After moving our source tree from VSS to SVN, I can no longer
get ecosconfig to work.  It always used to configure the
"current" version by default.  Now it uses v2_0 of a packate if
it's available and current if it's not.

If I try to tell ecosconfig to use the current version it
complains:

    $ ecosconfig new dm2 net current
    
    Usage: ecosconfig [ qualifier ... ] [ command ]
      commands are:
        list                                       : list repository contents
        new TARGET [ TEMPLATE [ VERSION ] ]        : create a configuration
        target TARGET                              : change the target hardware
        template TEMPLATE [ VERSION ]              : change the template
      [...]

If I leave off the "current", it selects v2_0 (which won't
configure/build because of conflicts between packages).

So I've got two questions

 1) What would cause ecosconfig to decided it likes v2_0 better
    than current?

 2) How do I tell it I want current? 
      
-- 
Grant Edwards                   grante             Yow! I wonder if I could
                                  at               ever get started in the
                               visi.com            credit world?


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [ECOS]  Re: can't get ecosconfig to use "current" version
  2007-05-22 14:39 [ECOS] can't get ecosconfig to use "current" version Grant Edwards
@ 2007-05-22 16:27 ` Grant Edwards
  2007-05-22 20:06 ` Grant Edwards
  1 sibling, 0 replies; 3+ messages in thread
From: Grant Edwards @ 2007-05-22 16:27 UTC (permalink / raw)
  To: ecos-discuss

On 2007-05-22, Grant Edwards <grante@visi.com> wrote:

> After moving our source tree from VSS to SVN, I can no longer
> get ecosconfig to work.  It always used to configure the
> "current" version by default.  Now it uses v2_0 of a package if
> it's available and current if it's not.

I had to remove templates/net/v2_0.ect.  After removing that
file, ecosconfig defaulted to "current".

Why was ecosconfig choosing templates/net/v2_0.ect instead of 
templates/net/current.ect?

-- 
Grant Edwards                   grante             Yow! I just forgot my whole
                                  at               philosophy of life!!!
                               visi.com            


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [ECOS]  Re: can't get ecosconfig to use "current" version
  2007-05-22 14:39 [ECOS] can't get ecosconfig to use "current" version Grant Edwards
  2007-05-22 16:27 ` [ECOS] " Grant Edwards
@ 2007-05-22 20:06 ` Grant Edwards
  1 sibling, 0 replies; 3+ messages in thread
From: Grant Edwards @ 2007-05-22 20:06 UTC (permalink / raw)
  To: ecos-discuss

On 2007-05-22, Grant Edwards <grante@visi.com> wrote:

> If I try to tell ecosconfig to use the current version it
> complains:
>
>     $ ecosconfig new dm2 net current
>     
>     Usage: ecosconfig [ qualifier ... ] [ command ]
>       commands are:
>         list                                       : list repository contents
>         new TARGET [ TEMPLATE [ VERSION ] ]        : create a configuration
>         target TARGET                              : change the target hardware
>         template TEMPLATE [ VERSION ]              : change the template
>       [...]
>
> If I leave off the "current", it selects v2_0 (which won't
> configure/build because of conflicts between packages).
>
> So I've got two questions
>
>  1) What would cause ecosconfig to decided it likes v2_0 better
>     than current?

Others have apparently run into this and haven't been able to
find an answer either.

>  2) How do I tell it I want current? 

This seems to be a known problem:

  http://thread.gmane.org/gmane.os.ecos.general/17834/focus=17837

According to the above thread, the bug in command-line parsing
that is rejecting the version specifier has been fixed. But,
I'd still like to know how ecosconfig decides what version it's
going to build by default.  I've searched the Users Guide, the
Reference Guide, and the Component Writers Guide, and didn't
find any documentation on ecosconfig other than a few examples.

-- 
Grant Edwards                   grante             Yow! My BIOLOGICAL ALARM
                                  at               CLOCK just went off ... It
                               visi.com            has noiseless DOZE FUNCTION
                                                   and full kitchen!!


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-05-22 16:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-22 14:39 [ECOS] can't get ecosconfig to use "current" version Grant Edwards
2007-05-22 16:27 ` [ECOS] " Grant Edwards
2007-05-22 20:06 ` Grant Edwards

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).