Subject:*
Name/Email:*
Message Icon:*
Message:*
url email imgsrc image php hide code quote
English Nederlands 
SAMPLE
alignleft aligncenter alignright bold italic underline linethrough   


 [more...]
Options:*
 

 

 
View requirements*
Reply No requirement
Confirmation Code*
  The code is case-insensitive  Click the image for a new code. | Maximum attempts: 8
     
Re: Not commiting my own mainfile - Please help me !!!

by marcan on 2007/12/6 6:15:17

Oh I understand now steve. Yes this could work.

Anyway, again :
Quote:

So the best thing is probably to accept that our mainfile on the SVN will get changed from time to time, but we can live with it. We can always revert the changes, it's no big deal...



Re: Not commiting my own mainfile - Please help me !!!

by skenow on 2007/12/6 4:54:42

marcan - I only export to another directory when I start, not for every edit. I make changes and test in my copy and when I am satisfied, I make the changes to the sandbox copy and commit.

Leaving the mainfile out of the distribution is OK with me, as long as the installation processes still work.
Re: Not commiting my own mainfile - Please help me !!!

by davidl2 on 2007/12/6 4:17:18

Just have to try and remember ... just like I need to remember to comment any changes
Re: Not commiting my own mainfile - Please help me !!!

by marcan on 2007/12/6 4:09:59

Quote:

I have only worked with SVN/CVS a little, so I export a copy of my sandbox to my local server for testing. When I'm happy with it, I merge the changes into my sandbox copy, then commit to the repository.


I personally cannot work like that as I usually practically test my changes after each line... So I would not export it every time.

So creating mainfile at installation can be an idea. But the permissions are an issue I think...

So the best thing is probably to accept that our mainfile on the SVN will get changed from time to time, but we can live with it. We can always revert the changes, it's no big deal...
Re: Not commiting my own mainfile - Please help me !!!

by JMorris on 2007/12/6 4:01:05

Quote:


Dave_L wrote:
Another approach could be to not include a mainfile.php in the distribution package; the file would be created during installation. But that introduces another complication: the directory containing mainfile.php would have to be writable.



That kind of approach is rather commonplace among my systems and the directory would have to be writable anyways in order to write to cache and templates_c.

Not including mainfile.php and generating it during install sounds pretty logical.