[MonoDevelop] [Fwd: Re: Deploy to tarball]

[Scott Ellington]

Well since you have configurations for your application which are per
user, you would probably want to copy it into a directory in the user's
home directory (i.e. /home/myuser/...).  It could be in .myapp/
or .config/ or whatever.

You would do this in your application the first time it is started.

Scott

On Sun, 2006-08-20 at 15:05 -0400, Carlos J. Muentes wrote:
> I do have one more issue:
> 
>     This application has a config file that must be writeable by the
> user running the app, in order for configuration parameters to be
> mutable.  make install seems to default to installing
> to /usr/local/bin and /usr/local/lib, which when running as a normal
> user, this file becomes read-only.  How can I solve this?  I know I
> can add --prefix to configure, but then the full path to the app
> start-up script must be used when invoking the application.  This
> seems to be a bit sub-par IMHO; what does everyone else think?  My
> absolute goal here is to make this app easy to install, easy to
> invoke, while avoiding issues that arise from system permissions due
> to install location/invoking user.
> 
> 
> On Sat, 2006-08-19 at 15:22 +0000, Scott Ellington wrote: 
> > forgot to copy the group
> > email message attachment, "Forwarded message - Re: [MonoDevelop]
> > Deploy to tarball"
> > > -------- Forwarded Message --------
> > > From: Scott Ellington <scottell.lists at gmail.com>
> > > To: Carlos J. Muentes <carlos at rockwithme.org>
> > > Subject: Re: [MonoDevelop] Deploy to tarball
> > > Date: Sat, 19 Aug 2006 14:15:57 +0000
> > > 
> > > Hi,
> > > 
> > > Your problem is not related to generics.  You have non-code files in
> > > your solution which are flagged to be compiled.
> > > 
> > > >From what I can see, this includes some xml config files, a readme.txt,
> > > and an App.Config.  I am not sure why MonoDevelop builds these projects
> > > successfully, but you need to unflag these files for autotools.
> > > 
> > > I think what you want to do is flag them for deployment.  This is
> > > something Lluis did which is pretty cool.  This will deploy these files
> > > to the install directory (i.e. .../lib/myapp/ )
> > > 
> > > To do this, right click on the files in the solution pad, and select
> > > 'Deploy' from the 'Include' submenu.  This will uncheck the 'Build'
> > > option.  For files that you don't want to deploy (maybe readme.txt) just
> > > uncheck the 'Build' option.
> > > 
> > > I had to commit a small fix for the exe wrapper, but after that your app
> > > deployed, built, and ran fine.
> > > 
> > > let me know if there are any more problems,
> > > Scott
> > > 
> > > 
> > > 
> > > On Sat, 2006-08-19 at 10:10 -0400, Carlos J. Muentes wrote:
> > > > Here's my solution.
> > > > 
> > > > 
> > > > On Sat, 2006-08-19 at 09:56 +0000, Scott Ellington wrote: 
> > > > > Can you mail me your solution?  Or make up a test case?
> > > > > 
> > > > > thanks,
> > > > > Scott
> > > > > 
> > > > > On Sat, 2006-08-19 at 08:19 -0400, Carlos J. Muentes wrote:
> > > > > >     I got latest from SVN, but it's still failing with a 'parsing
> > > > > > error' message, what am I missing?  I've got a deploy to tarball
> > > > > > target configured for the solution (which I recreated once I was in
> > > > > > the newest MD instance), which contains two projects; both of which
> > > > > > are configured to use the 2.0 runtime.  Like I said, the solution
> > > > > > builds and runs fine in MD, and I've also built an installer for
> > > > > > Windows (using Innosetup) that runs fine as well.
> > > > > > 
> > > > > >     I went into the
> > > > > > monodevelop/Extras/CSharpBinding/Autotools/CSharpAutotoolsSetup.cs
> > > > > > file, and confirmed the check for 2.0 runtime was there, and it was,
> > > > > > but running make still makes it apparent that it's not in fact
> > > > > > targeting the 2.0 runtime.  Not sure what to do at this point . . .
> > > > > > 
> > > > > > 
> > > > > > On Fri, 2006-08-18 at 10:41 +0000, Scott Ellington wrote: 
> > > > > > > Hi,
> > > > > > > 
> > > > > > > I'd forgotten about this, but it appears Lluis added this functionality
> > > > > > > about a month ago:
> > > > > > > 
> > > > > > > http://svn.myrealbox.com/viewcvs/trunk/monodevelop/Extras/CSharpBinding/Autotools/CSharpAutotoolsSetup.cs?rev=62683&r1=61764&r2=62683
> > > > > > > 
> > > > > > > I was able to create a test solution which uses Generics, generate
> > > > > > > autotools, and build with make successfully.  Make sure you are using an
> > > > > > > updated SVN and that you have set your project to the 2.0 runtime.
> > > > > > > 
> > > > > > > Scott
> > > > > > > 
> > > > > > > On Fri, 2006-08-18 at 00:33 -0400, Carlos J. Muentes wrote:
> > > > > > > > Hey all,
> > > > > > > > 
> > > > > > > >     I added a tarball deployment target to a project I built in
> > > > > > > > MD.  ./configure runs fine, but make fails with a parsing error (due
> > > > > > > > to generics).  The project targets the 2.0 runtime (and compiles and
> > > > > > > > runs fine in MD), but the tarball doesn't seem to be configured to
> > > > > > > > compile against the 2.0 runtime.  What am I missing? 
> > > > > > > > _______________________________________________
> > > > > > > > Monodevelop-list mailing list
> > > > > > > > Monodevelop-list at lists.ximian.com
> > > > > > > > http://lists.ximian.com/mailman/listinfo/monodevelop-list
> > > > > > > 
> > > > > > > 
> > > > > 
> > > > > 
> > _______________________________________________
> > Monodevelop-list mailing list
> > Monodevelop-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/monodevelop-list