Cannot init new project on Mono

[konrad-kruczynski]

I've just built (using MSBuild) the newest version of openwrap-shell from sources and used it on Linux/Mono.

The shell installed without errors, but when doing o init-wrap TestProject -git (I have made a launcher for openwrap shell named 'o' to mimic usage available in Windows - would be nice to do that during installation on Linux/OSX, but this is subject for another issue ;))

Anyway, the effects are:

# OpenWrap v1.0.0+0 (shell v2.1.0)
Specify either the path to the projects you want updated or -all to find all projects automatically.
No such file or directory
konrad@ubuntu:~$ ls TestProject/
src  wraps

and unusable init is its effect, which can be seen here:

konrad@ubuntu:~/TestProject$ o add-wrap log4net
# OpenWrap v1.0.0+0 (shell v2.1.0)
Project repository doesn't exist but -project has been specified.

[konrad-kruczynski]

There is similar problem with initialization on existing project:

konrad@ubuntu:~/Test3$ o init-wrap -all
# OpenWrap v1.0.0+0 (shell v2.1.0)
No such file or directory

[serialseb]

There's an issue with localising the system repository on Linux, not had the time to investigate yet.

You want to make sure you use 2.0.3 or above for unix though, this code shows 1.0

Sebastien Lambla

On 25 May 2012, at 21:26, "Konrad Kruczyński" reply@reply.github.com wrote:

I've just built (using MSBuild) the newest version of openwrap-shell from sources and use it on Linux/Mono.

The shell installed without errors, but when doing o init-wrap TestProject -git (I have made a launcher for openwrap shell named 'o' to mimic usage available in Windows - would be nice to do that during installation on Linux/OSX, but this is subject for another issue ;))

Anyway, the effects are:

# OpenWrap v1.0.0+0 (shell v2.1.0)
Specify either the path to the projects you want updated or -all to find all projects automatically.
No such file or directory
konrad@ubuntu:~$ ls TestProject/
src  wraps

and usable init is its effect, which can be seen here:

konrad@ubuntu:~/TestProject$ o add-wrap log4net
# OpenWrap v1.0.0+0 (shell v2.1.0)
Project repository doesn't exist but -project has been specified.

---

Reply to this email directly or view it on GitHub:
#321

[konrad-kruczynski]

I see, can I update it via open-wrap (the 1.0 version was installed with the newest shell)?

[serialseb]

1.0 gets downloaded automatically. If you have a 2.0 package you can try updating the system by copyin the package to your current directory and update-wrap OpenWrap -sys

Sebastien Lambla

On 25 May 2012, at 21:37, "Konrad Kruczyński" reply@reply.github.com wrote:

I see, can I update it via open-wrap (the 1.0 version was installed with the newest shell)?

---

Reply to this email directly or view it on GitHub:
#321 (comment)

[konrad-kruczynski]

Thanks for the feedback. I've used the freshly compiled wrap to update using the command you've provided. It looks to be updated but strange problem emerges:

konrad@ubuntu:~/Desktop$ o init-wrap myProject
# OpenWrap v2.0.3+26 (shell v2.1.0)
The term 'init-wrap' is not a recognized command or alias. Check the spelling or enter 'get-help' to get a list of available commands.
konrad@ubuntu:~/Desktop$ o get-help
# OpenWrap v2.0.3+26 (shell v2.1.0)
The term 'get-help' is not a recognized command or alias. Check the spelling or enter 'get-help' to get a list of available commands.

Do you have any ideas? Is there a place I can find the ready-made wraps (maybe I should use a little bit older version)? Pardon the questions, but I'm new to OpenWrap (which looks promising).

[konrad-kruczynski]

I've returned to 1.0 using -ShellPanic, but don't know to which version should I upgrade. Just for the record, here's the process of upgrading:

# OpenWrap v1.0.0+0 (shell v2.1.0)
Searching for updated packages...
System repository: openwrap updated [1.0.2.86964541 -> 2.0.3.26].
System repository: SharpZipLib up-to-date.
System repository: Mono.Cecil up-to-date.
System repository: tdnet-framework up-to-date.
System repository: openfilesystem up-to-date.

[serialseb]

Latest compiled ones are on teamcity, http://teamcity.caffeine-it.net

Sebastien Lambla

On 25 May 2012, at 22:04, "Konrad Kruczyński" reply@reply.github.com wrote:

Thanks for the feedback. I've used the freshly compiled wrap to update using the command you've provided. It looks to be updated but strange problem emerges:

konrad@ubuntu:~/Desktop$ o init-wrap myProject
# OpenWrap v2.0.3+26 (shell v2.1.0)
The term 'init-wrap' is not a recognized command or alias. Check the spelling or enter 'get-help' to get a list of available commands.
konrad@ubuntu:~/Desktop$ o get-help
# OpenWrap v2.0.3+26 (shell v2.1.0)
The term 'get-help' is not a recognized command or alias. Check the spelling or enter 'get-help' to get a list of available commands.

Do you have any ideas? Is there a place I can find the ready-made wraps (maybe I should use a little bit older version)? Pardon the questions, but I'm new to OpenWrap (which looks promising).

---

Reply to this email directly or view it on GitHub:
#321 (comment)

[konrad-kruczynski]

I've managed to find an older version but results are the same:

konrad@ubuntu:~/Desktop/wraps$ o get-help
# OpenWrap v2.0.0+1 (shell v2.1.0)
The term 'get-help' is not a recognized command or alias. Check the spelling or enter 'get-help' to get a list of available commands.

so the subject of this issue should be rather something like general problem with 2.0 on Linux? But as far as I understood this is the specific version that should work.

[konrad-kruczynski]

More information:
When I am in a directory containing openwrap sources (checked out from git), the get-help works fine:

konrad@ubuntu:~/gits/openwrap$ o get-help
# OpenWrap v2.0.3+26 (shell v2.1.0)

List of available commands
--------------------------

Usage:
  o {{verb}}-{{noun}} <command-arguments>

configuration
 > get: Returns a list of all configured data.
   remove: Clears configuration data.
   set: Gets or sets configuration data, such as network proxy credentials and names.

gui
   open: Opens the OpenWrap Dashboard

help
 > get: Provides documentation for the commands available in the current OpenWrap session.

nuget
   convert: Converts a NuPack legacy package into an OpenWrap package.

remote
 > list: Lists the configured remote repositories.

(output truncated).

Is it the problem with repository localising you've mentioned earlier?

[konrad-kruczynski]

More feedback on that: I've manually created the equivalent of the initial structure of the project (created by init-wrap) using files from the OpenWrap git repository. Then OpenWrap seems to be working quite well:

konrad@ubuntu:~/Desktop/SomeTest$ o add-remote nuget
# OpenWrap v2.0.3+26 (shell v2.1.0)
Remote repository 'nuget' added.
konrad@ubuntu:~/Desktop/SomeTest$ o add-wrap ELFSharp
# OpenWrap v2.0.3+26 (shell v2.1.0)
Using descriptor SomeTest.wrapdesc.
Project repository present.
Dependency 'ELFSharp' added successfully.

[konrad-kruczynski]

My joy was a little premature. In fact the after o add-wrap and OpenWrap's output presented above it hanged.

Anyway I think that the issues should be resolved one after one, so if the get-help problem described above is the example of mentioned localising issue, can you point me to this issue so I'll be able to watch it?

[konrad-kruczynski]

However, for the record: the hang issue (maybe very slow operation?) was probably due to the nuget repository added. After removing it the output is

konrad@ubuntu:~/gits/openwrap$ o add-wrap log4net
# OpenWrap v2.0.3+26 (shell v2.1.0)
Using descriptor openwrap.wrapdesc.
Project repository present.
Dependency 'log4net' added successfully.
Package log4net not found in any repository.
konrad@ubuntu:~/gits/openwrap$ 

[konrad-kruczynski]

After some more experiments I can say that adding nuget repository and installing packages from them works on Mono/Linux, although it is very time consuming process (and because of that I thought it hanged). Nevertheless I tried Windows/.NET afterwards and it was behaving that way too, so this is not related to Mono.

So, to sum up - I think the only problem left is the project initialization; if I fake the initialization by manually copying/editing files, everything works fine (well, more or less fine, but still the same way as in Windows/.NET).

[serialseb]

Cool. The nuget problem should be fully resolved by this evening when cached repositories land.

Sebastien Lambla

On 29 May 2012, at 00:25, "Konrad Kruczyński" reply@reply.github.com wrote:

After some more experiments I can say that adding nuget repository and installing packages from them works on Mono/Linux, although it is very time consuming process (and because of that I thought it hanged). Nevertheless I tried Windows/.NET afterwards and it was behaving that way too, so this is not related to Mono.

So, to sum up - I think the only problem left is the project initialization; if I fake the initialization by manually copying/editing files, everything works fine (well, more or less fine, but still the same way as in Windows/.NET).

---

Reply to this email directly or view it on GitHub:
#321 (comment)