savannah-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-dev] [bug #1736] Problems with code organization


From: nobody
Subject: [Savannah-dev] [bug #1736] Problems with code organization
Date: Sat, 08 Nov 2003 05:09:23 -0500
User-agent: Mozilla/5.0 (compatible; Konqueror/3; Linux 2.4.18-27.7.x.cern; i686)

=================== BUG #1736: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1736&group_id=11

Changes by: Mathieu Roy <address@hidden>
Date: sam 08.11.2003 à 11:09 (Europe/Paris)

            What     | Removed                   | Added
---------------------------------------------------------------------------
            Category | PHP Engine                | Installation Process
            Severity | 5 - Average               | 1 - Enhancement
            Priority | None                      | Later
         Assigned to | villate                   | None


------------------ Additional Follow-up Comments ----------------------------
[unassign bug to open the door to contribution] 



=================== BUG #1736: FULL BUG SNAPSHOT ===================


Signalé par: berezin                  Projet: Savannah                      
Signalé le: dim 17.11.2002 à 01:14
Category:  Installation Process       Severity:  1 - Enhancement            
Priority:  Later                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Fixed Release:                        

Summary:  Problems with code organization

Original Submission:  Hello again,



As I'm configuring Savannah locally, I found the following

problems which potentially may cause inconvenience to me

and others.



1. Local configuration scripts modify CVS'ed files and even

   *themselves* (specifically, savannah/gnuscripts/sv_*,

   savannah/www/css/*.css).



   If someone modifies those files at savannah.gnu.org,

   I will have trouble merging the diffs with my 

   site-specific changes.



   I think, such files should be generated,

   say, from *.in files, much like Makefile.in,

   and not modified in place.



2. The binary 'savannah/gnuscripts/Mailman/sfverify'

   is checked in to CVS, but I found no sources!

   (Hello, GNU police! :-)

   Fortunately, I could make use of 'sfverify.py'. 



3. This is probably minor, but still annoying:



   savannah/gnuscripts/Mailman/mailing_lists_create.pl



   I use sendmail, and in '/etc/aliases'

   sendmail wants the "|command" part to be in double

   quotes.  I had to change lines like those:



     print ALIAS "$listname-admin: |$wrapper mailowner $listnamen";



   to make them look like this:



     print ALIAS "$listname-admin: "|$wrapper mailowner $listname"n";



Cheers,



Sergey.



Follow-up Comments
*******************

-------------------------------------------------------
Date: sam 08.11.2003 à 11:09        By: yeupou
[unassign bug to open the door to contribution] 

-------------------------------------------------------
Date: sam 30.11.2002 à 12:41        By: yeupou
On the first point : make update-path or make reset-path handle this matters. 


La liste CC est vide


Il n'y a aucun fichier attaché actuellement


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=1736&group_id=11

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]