Hello all,
As I couldn't find anything on this specific issue, better ask...
After being able to compile my code with help of autotools, now i want to
deliver it as a package. In this case I dont want to give out my configure.ac
and Makefile.ams in order to avoid some extra fiddling from others.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 5:34 AM:
> Hello all,
>
> As I couldn't find anything on this specific issue, better ask...
> After being able to compile my code with help of autotools, now i want to
> deliver it as a package. In this cas
On Thu, 21 Aug 2008, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 5:34 AM:
Hello all,
As I couldn't find anything on this specific issue, better ask...
After being able to compile my code with help of autotools, now i want to
deli
>
> If it's _his_ source code (and assuming that _he_ licensed it GPL), he can
> distribute whatever set of files he chooses. The restriction applies for
> files that he gets from someone else.
>
yes it's pure my code and i haven't licenced it yet(didn't have time for that).
Having
cleared th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 8/21/2008 6:51 AM:
>> If it's _his_ source code (and assuming that _he_ licensed it GPL), he can
>> distribute whatever set of files he chooses. The restriction applies for
>> files that he gets from someone else.
>
On Thu, 21 Aug 2008, Thomas Dickey wrote:
If it's _his_ source code (and assuming that _he_ licensed it GPL), he can
distribute whatever set of files he chooses. The restriction applies for
files that he gets from someone else.
If no one else is allowed to distribute the package, then what'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Friesenhahn wrote:
> On Thu, 21 Aug 2008, Thomas Dickey wrote:
>>
>> If it's _his_ source code (and assuming that _he_ licensed it GPL), he
>> can distribute whatever set of files he chooses. The restriction
>> applies for files that he gets from
First of all many thanks for numerous replies.
- original Nachricht
>
> I have to agree with Bob here. There's only one reason for not
> distributing configure.ac and Makefile.am -- because you're trying to
> keep others from modifying your build system.
>From the very beginning
Hello,
* [EMAIL PROTECTED] wrote on Thu, Aug 21, 2008 at 06:07:22PM CEST:
>
> >From the very beginning, lies my intention in this point: As there are
> features to correct and implement, I do not want to have any extra
> headaches from the svn users like "Oh, i can't `make install` it here"
> and
On 21-Aug-2008, [EMAIL PROTECTED] wrote:
| >From the very beginning, lies my intention in this point: As there are
| features to correct and implement, I do not want to have any extra
| headaches from the svn users like "Oh, i can't `make install` it here"
| and then i have to troubleshoot that al
On Thu, 2008-08-21 at 18:07 +0200, [EMAIL PROTECTED] wrote:
> Well till i get things running, i dont want to get anyone fiddle around with
> the build system, that's all. After that, i'd appreciate if anyone comes up
> with a patch, change whatever it is. Help is always welcomed to give
> and take.
Hello,
* Tim Post wrote on Fri, Aug 22, 2008 at 05:21:04AM CEST:
>
> 2 - People updating their svn / git / hg from your's may actually have
> to solve merge conflicts in configure itself, which is a __major__ pain
> in the butt. This happens if they have run 'autoreconf' themselves, or
> similar.
12 matches
Mail list logo
