in msg:

-|- Irssi: Starting query in freenode with SloMo_
<SloMo_> hi... i'm currently working together with the maintainer of the nemerle debian 
          package to let it comply with these policies: https://wiki.ubuntu.com/CLIPolicy
<SloMo_> are these the latest? and where do the .exe files belong when upstreams normally 
          installs them into /usr/bin... /usr/lib/dotnet/bin and links to cli-wrapper in 
          /usr/bin? or leaving the upstream locations?

/me wakes up
< tseng> slomo: no
< tseng> slomo: /usr/share/dotnet is deprecated (and this is mentioned in our CLIPolicy)
< tseng> slomo: put the stuff where upstream does
< slomo> tseng: so the .exe files and the cli-wrapper links will live side-by-side in 
          /usr/bin ;) thanks, will do that
< tseng> slomo: no?
< tseng> they wont
< tseng> .exe does NOT go in /usr/bin
< tseng>  /usr/lib/muine/muine.exe
< tseng> etc
< tseng> (what does cli-wrapper have to do with this?)
< slomo> yes when the upstream buildsystem does it that way... but that isn't the case 
          with nemerle. they put the .exe in the bindir which is /usr/bin when not 
          specified otherwise
< tseng> well in that case they are wrong
< tseng> would you and the maintainer like to join #debian-mono?
< tseng> meebey maintains monodevelop, he is probably also interested in what you do with 
          it
< slomo> ok, and what will be the right way to package it? (and cli-wrapper was used to 
          create the binaries without .exe suffix in /usr/bin)
< tseng> well what every other package i work with does
< tseng> is make /usr/lib/foo/foo.exe
< tseng> and put a shell script in /usr/bin
< tseng> that properly sets up the evironment and calls mono on the exe
< tseng> would you and the maintainer like to join #debian-mono?
< tseng> meebey maintains monodevelop, he is probably also interested in what you do with 
          it
< slomo> ok, and what will be the right way to package it? (and cli-wrapper was used to 
          create the binaries without .exe suffix in /usr/bin)
< tseng> well what every other package i work with does
< tseng> is make /usr/lib/foo/foo.exe
< tseng> and put a shell script in /usr/bin
< tseng> that properly sets up the evironment and calls mono on the exe
-|- anibal [ams@ns1.mssinc.biz] has joined #ubuntu-motu
< slomo> so the best would be to create a patch for the buildsystem and send it upstream? 
          (i'll join #debian-mono later, currently working on other things)
-|- mehrfachstecker [~aldomansk@p54AFB167.dip0.t-ipconnect.de] has joined #ubuntu-motu
< tseng> id like to have meebey's opinion also, before we start kicking upstream
< \sh> k....breezy is vmware compatible
< tseng> slomo: thanks.