I'd like to suggest a development package that can be updated in the repository and contains all the necessary contexts. Then a developer could do something like:
~/.rmakerc: includeConfigFile /etc/foresight/development/rmake.config ~/.conaryrc: includeConfigFile /etc/foresight/development/conary.confg Those are probably terrible suggestions for the names of the files, but you get the idea. Then people wouldn't have to keep copying changed context data from a wiki page. On Tue, May 19, 2009 at 10:34:44AM -0400, Og Maciel wrote: > Hi guys, > > I've just closed IT-75. The context information for developers wanting > to package for Foresight against the 2-devel label has now been > updated. You can browse it here: > http://www.foresightlinux.org/hg/foresight-devel-contexts/file/41cf734d70bc/2-devel/ > > Can we all agree to promote it (a web page should be coming shortly) > so that new developers have an easier entry point into the packaging > world? Also, we need to make sure we keep it up to date. > > Cheers, > -- > Og B. Maciel > > [email protected] > [email protected] > [email protected] > > GPG Keys: D5CFC202 > > http://www.ogmaciel.com (en_US) > http://blog.ogmaciel.com (pt_BR) > _______________________________________________ > Foresight-devel mailing list > [email protected] > http://lists.rpath.org/mailman/listinfo/foresight-devel _______________________________________________ Foresight-devel mailing list [email protected] http://lists.rpath.org/mailman/listinfo/foresight-devel
