Re: Warp: RSS Package Manager
"Neil Munro" <[email protected]>
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
2008/5/28 Isak Savo <[email protected]>: > On Tue, May 27, 2008 at 11:25 PM, Neil Munro <[email protected]> wrote: > > Hey all, I was wondering what you guys thought of this. > > > > http://www.sourceforge.net/projects/warp > > > > It's my own project and while I know I have not put out a new release in > a > > few months I have had exams so had to revise for them, but work has > > continued, and I have one new feature to implement before the new version > > comes out, I would like to point out the first package format I > implemented > > was in fact autopackage support because my theory is when a new > autopackage > > comes out Warp will automatically check remove the old version and > install > > the new version. I figure it's easier for the user to have a program to > > automatically update their autopackages than searching for them manually. > > Cool, so you mentioned it was written in c#. Did it work well to > package mono applications with autopackage? I've been meaning to add > better support for mono based apps in autopackage for a while and it'd > be interesting to hear your issues. I do not know HOW to autopackage anything, I tried to package pidgin once and could not do it. I have very little understanding of how autopackage actually works, if someone can help me package it I will try, if only to help discover the potential issues packaging a mono app might show up. > > > Warp aim's to bridge the gap between distributions not adding new > features > > until a new release and users wanting new features in the interim. It's > > written in C# and uses bash calls occasionally to work on Nix systems. > > Just curious, why do you need to call bash? You should have access to > pretty much the entire POSIX api (or equivalent .NET api) from mono. The API is very complicated and including the mono namespaces created a dependency on them which resulted in the source not compiling under windows. My main issue was setting permissions, it involved bitwise operations which while I had a vague understanding of what was happening I wasn't fully aware of what to do. It was mostly setting a script file or autopackage to be executable that was the problem. So I created a process that called chmod. > > > > It's > > worth pointing out the code I have on my hard drive is much cleaner and > > better than what's on sourceforge at the moment, but I do not know how to > > use svn or cvs and can't understand the sourceforge documents on how to > make > > it work. > > Sounds like you should take a look at the svnbook. > http://svnbook.red-bean.com/ Taking a read now. Thanks. > <http://svnbook.red-bean.com/> > > -Isak > > --------------------------------------------------------------------- > To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] > For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected] > >