Thierry, I'm the developer working on the Windows port, but my efforts right now are targeted toward the shell integration as opposed to the Windows installer. If you'd like to take a first cut at creating a setup project that'd be awesome. Please make sure to include the merge module from TortoiseOverlays.
Virtual machines are the ideal way to test this (and the only way I'll test a Windows XP setup anyways). Thanks, Stefan On Tue, May 31, 2011 at 2:56 PM, Team Odev <[email protected]> wrote: > Hi Philipp, > > It's a long time I haven't built rpms - I know the principles of building > them but it's a very basic - poor - knowledge. Tell me if no one can help, > and I'll check my records ... > > I thought that a member of the Syncany team was currently working on a > windows port on a separate branch ? > > For Windows setup.exe, I often use inno setup (for my job) and I can start > writing an inno setup script for installing Syncany with ? Maybe in > collaboration with the developer working on the Windows port ? > > An idea for testing the package : an efficient solution is to test on > virtual machines ( Virtual boxes ) : fresh / base install of the Operating > System, then take a reference snapshot before testing the Syncany package > installation. Reverting to the snapshot is fast, and allows to test again as > if we were in a fresh install. > > Best Regards, > > Thierry > > > > 2011/5/31 Philipp Heckel <[email protected]> > >> Hey all, >> >> Regarding the dependencies: I tried to simply the dependency-issues by >> (temporarily) adding all required JARs (except java-gnome) to the >> 'lib' folder. That makes it easier for the Windows version and for >> development. >> >> @Thierry: No there is no functional version on Windows yet. >> >> I have used Inno Setup before. It's a great Tool for creating >> setup-files. I think we should start thinking about packaging. On >> Linux (*.deb, *.rpm), and on Windows a setup.exe. >> >> Do you (or anybody else) have experience with either one of them? >> >> Cheers, >> Philipp >> >> On Tue, May 31, 2011 at 10:04 AM, Philipp Heckel >> <[email protected]> wrote: >> > Hey Stefan, >> > >> > that's what I thought... I currently do not store the JARs in the repo >> > at all, but I'll add then later so you don't have to assemble them :-) >> > >> > Cheers, >> > Philipp >> > >> > On Tue, May 31, 2011 at 4:04 AM, Stefan Mai <[email protected]> >> wrote: >> >> Philipp, >> >> When you build Syncany under Windows, where in the repository are you >> >> storing dependencies? I'm having a bit of trouble assembling the >> correct >> >> versions of all the missing jars. >> >> Thanks, >> >> Stefan >> >> >> >> On Mon, May 30, 2011 at 6:04 AM, Philipp Heckel < >> [email protected]> >> >> wrote: >> >>> >> >>> Hi everyone, >> >>> >> >>> With regard to the variety of Linux distributions and other OSs >> >>> Syncany is (hopefully) going to be used on, I think we need to do some >> >>> sort of dependency management. Some packages are available on some >> >>> systems, others are not. Especially on Windows (and OSX?), all >> >>> dependencies have to be shipped with the application. >> >>> >> >>> Does anybody know how other projects do that? >> >>> >> >>> >From the top of my head, I'd suggest to have all required JARs in the >> >>> library folder and write different Ant scripts for the different >> >>> platforms. However, that would mean that the library folder would >> >>> become very large very quickly... >> >>> >> >>> Any other ideas? Comments? Anybody interested in doing that? Would be >> >>> of great help! >> >>> >> >>> I think the above dependency issues are also relevant for the plugins >> >>> and their dependencies. I believe carrying around all the plugins with >> >>> the main application is not a good thing, because most people will use >> >>> only one or two of them. I think it would be great to have one JAR >> >>> file per plugin and the possibility to put them in a plugin folder >> >>> (e.g. ~/.syncany/plugins). >> >>> >> >>> Again, I could really use some help with this so I can concentrate on >> >>> the main synchronization algorithm. >> >>> >> >>> Cheers, >> >>> Philipp >> >>> >> >>> -- >> >>> Mailing list: https://launchpad.net/~syncany-team >> >>> Post to : [email protected] >> >>> Unsubscribe : https://launchpad.net/~syncany-team >> >>> More help : https://help.launchpad.net/ListHelp >> >> >> >> >> > >> >> >> >> -- >> H3 11, 68159 Mannheim, Germany >> Landline: +49-621-98181881 / Cell phone: +49-173-7865012 (o2 network) >> Public Key: 0xBD5E122F at pgp.mit.edu >> >> -- >> Mailing list: https://launchpad.net/~syncany-team >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~syncany-team >> More help : https://help.launchpad.net/ListHelp >> > > > -- > Mailing list: https://launchpad.net/~syncany-team > Post to : [email protected] > Unsubscribe : https://launchpad.net/~syncany-team > More help : https://help.launchpad.net/ListHelp > >
-- Mailing list: https://launchpad.net/~syncany-team Post to : [email protected] Unsubscribe : https://launchpad.net/~syncany-team More help : https://help.launchpad.net/ListHelp
