delorie.com/archives/browse.cgi | search |
Date: | Sat, 9 Dec 2000 14:55:26 -0500 |
Message-Id: | <200012091955.OAA30446@envy.delorie.com> |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <NBBBIOJKJBNCHJBEKHLOIEEBCCAA.tim.van.holder@pandora.be> |
Subject: | Re: CVS port |
References: | <NBBBIOJKJBNCHJBEKHLOIEEBCCAA DOT tim DOT van DOT holder AT pandora DOT be> |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> Now what I wanted to know is whether it is acceptable to base a DJGPP > package on development sources (i.e. on the latest CVS-based tree), Yes. As long as they're from CVS, they'll eventually become released sources. Note that this is a personal excemtion I make, and not normally allowed by the GPL. > is it acceptable to merge in unofficial patches (such as the > 'edit -c' patch that is used by CVSNT)? Since you're including full sources anyway, unofficial patches are allowed. Normally, though, they're discouraged as they make for maintenance headaches.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |