Changes

Jump to navigation Jump to search
Line 218: Line 218:     
* '''With no CVS write access'''
 
* '''With no CVS write access'''
With no write CVS access (with no savannah developer account), it is necessary to provide by mail a patch file to the developer mailing-list '''dolibarr-dev''' (See here for this https://savannah.nongnu.org/mail/?group=dolibarr). This is how to generate a patch file:  
+
With no write CVS access (with no savannah developer account), it is necessary to generate and send by mail a patch file to the developer mailing-list '''dolibarr-dev'''. This is how to generate a patch file:  
    
''For all OS:'' [[Image:Logo_windows.png|20px]] [[Image:Logo_ubuntu.png|20px]] [[Image:Logo_apple.png|20px]]
 
''For all OS:'' [[Image:Logo_windows.png|20px]] [[Image:Logo_ubuntu.png|20px]] [[Image:Logo_apple.png|20px]]
Line 245: Line 245:  
Finally, you will get a file ''mypatch.patch'' that contains all changes with goode format.
 
Finally, you will get a file ''mypatch.patch'' that contains all changes with goode format.
   −
* '''Test/Apply a patch'''
+
''Test/Apply a patch''
 
If you want to apply a patch file on an old version to have a new one modified by the path file, this is possible with the '''patch''' tool.
 
If you want to apply a patch file on an old version to have a new one modified by the path file, this is possible with the '''patch''' tool.
 
Imagine you have on non modified version somewhere on a server. Put you patch file into the root directory. Go into this root directory then launch the command:
 
Imagine you have on non modified version somewhere on a server. Put you patch file into the root directory. Go into this root directory then launch the command:
Line 255: Line 255:  
< is to provide source file name to use (patch must have format previsouly defined)
 
< is to provide source file name to use (patch must have format previsouly defined)
 
-u is to tell that patch has unified format</nowiki>
 
-u is to tell that patch has unified format</nowiki>
 +
 +
''Send patch by mail''
 +
Once patch file is built and successfully tested, you must submit file to the Dolibarr mailing list '''dolibarr-dev''' (See here for this https://savannah.nongnu.org/mail/?group=dolibarr).
 +
This mailing list is read by most Dolibarr developers, however we can't say if path will be processed nor that it will be included. It depends on quality of patch and priorities of moment.
    
= How to package and deploy a module =
 
= How to package and deploy a module =

Navigation menu