atom feed37 messages in com.selenic.mercurialRe: hgwebdir replacement - pylons hg app
FromSent OnAttachments
marcinkuzminskiJun 3, 2010 11:55 am 
Adrian BuehlmannJun 3, 2010 1:20 pm 
Jilles TjoelkerJun 3, 2010 2:00 pm 
Adrian BuehlmannJun 3, 2010 3:52 pm 
Mike MeyerJun 3, 2010 5:08 pm 
Adrian BuehlmannJun 3, 2010 5:27 pm 
Paul BoddieJun 4, 2010 1:35 am 
marcinkuzminskiJun 4, 2010 2:19 am 
Adrian BuehlmannJun 4, 2010 2:39 am 
Benoit BoissinotJun 4, 2010 2:42 am 
marcinkuzminskiJun 4, 2010 3:22 am 
Mike MeyerJun 4, 2010 7:24 am 
rupert.thurnerJun 6, 2010 4:33 am 
marcinkuzminskiJun 7, 2010 4:05 am 
marcinkuzminskiJun 7, 2010 7:30 am 
Bill BarryJun 7, 2010 1:30 pm 
marcinkuzminskiJun 7, 2010 2:28 pm 
Bill BarryJun 8, 2010 6:19 am 
marcinkuzminskiJun 8, 2010 1:10 pm 
marcinkuzminskiJun 29, 2010 12:22 pm 
DidlyJun 30, 2010 2:23 am 
marcinkuzminskiJun 30, 2010 2:54 am 
Alberto RodríguezJul 13, 2010 7:02 am 
marcinkuzminskiJul 13, 2010 7:59 am 
Alberto RodríguezJul 13, 2010 2:17 pm 
marcinkuzminskiJul 14, 2010 2:41 am 
marcinkuzminskiAug 17, 2010 3:36 pm 
Didly BomAug 18, 2010 12:29 am 
marcinkuzminskiAug 18, 2010 2:36 am 
Didly BomAug 18, 2010 3:38 am 
Alberto RodríguezAug 19, 2010 11:43 am 
marcinkuzminskiAug 19, 2010 12:26 pm 
marcinkuzminskiSep 23, 2010 4:55 am 
Didly BomSep 24, 2010 3:27 am.png
marcinkuzminskiOct 10, 2010 5:21 pm 
Adrian BuehlmannOct 11, 2010 12:00 am 
Alberto RodríguezOct 11, 2010 7:42 am 
Subject:Re: hgwebdir replacement - pylons hg app
From:Paul Boddie (paul@biotek.uio.no)
Date:Jun 4, 2010 1:35:17 am
List:com.selenic.mercurial

Adrian Buehlmann wrote:

Which is clearly not the case we are talking about here, so completely irrelevant.

vcs was defined as the library that calls mercurial via its python API.

What is unclear if you see

from mercurial import xxxx

in a python source?

Of course, if you have a variant of the vcs library that doesn't import from mercurial then you may slap whatever license you want to the end product (of course depends on what else *that* vcs depends on then).

The pertinent licensing restriction in action here can be observed when the software is actually used: the application in question must be licensed compatibly with the GPL so that the party running the application can modify/redistribute the system (application plus Mercurial) under the GPL. Thus, licensing the application alone under a GPL-compatible permissive licence should satisfy the terms of the GPL:

http://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL

What would be unacceptable here would be a GPL-incompatible licence for the application, such as one which allows for "non-commercial usage" only, or one which forbids access to or modification of the sources of the combined system, because the system as a whole would then not uphold the terms of the GPL.

Paul