On Apr 29, 2010, at 7:48 PM, NightStrike wrote:
> It's a lot easier to make the
> developers on your project use the right versions of stuff than
> imposing that requirement on all of your users. In my mind, our users
> should be able to download, configure, compile, and use. Creating the
> buil
On Thu, Apr 29, 2010 at 11:11 PM, Russ Allbery wrote:
> NightStrike writes:
>> On Thu, Apr 29, 2010 at 7:53 PM, Russ Allbery wrote:
>
>>> I suspect it depends on what sort of activities you expect people using
>>> a VCS checkout directly to be doing, and also how sophisticated of a
>>> VCS you'r
NightStrike writes:
> On Thu, Apr 29, 2010 at 7:53 PM, Russ Allbery wrote:
>> I suspect it depends on what sort of activities you expect people using
>> a VCS checkout directly to be doing, and also how sophisticated of a
>> VCS you're using. If you're using CVS, you basically can't do useful
>
On Thu, Apr 29, 2010 at 7:53 PM, Russ Allbery wrote:
> Bob Friesenhahn writes:
>
>> My project uses maintainer-mode and I always check these generated files
>> into the source code repository. The end user might not be able to
>> produce a working set of files based on whatever random autotools
Bob Friesenhahn writes:
> My project uses maintainer-mode and I always check these generated files
> into the source code repository. The end user might not be able to
> produce a working set of files based on whatever random autotools they
> have on their system.
I used to do this, but it quic
On Wed, 28 Apr 2010, Trevor Harmon wrote:
Yes, but that rule of thumb is at odds with another rule of thumb:
"Never commit generated files to a source code repository." And
considering that "autoreconf -i" does a perfect job of regenerating
all of the files I listed, I'm willing to break the
Hello,
I'm working on a project that we are converting to autotools and I had
a question. If this is the wrong place to ask these please direct me
to the right location.
Our project has a particle feature with three posible states:
STATIC, DYNAMIC, or NONE
Ideally we would like the build to b
Trevor Harmon writes:
> On Apr 29, 2010, at 12:25 AM, Russ Allbery wrote:
>> Although I must admit that now that I've switched to Git for
>> everything, I'm finding myself more and more just using git clean -x -f
>> -d
> What does that do?
Deletes every file and directory that isn't checked int
On Apr 29, 2010, at 12:25 AM, Russ Allbery wrote:
> Yeah, I've always ignored this part of the GCS for all of my projects. I
> don't think it makes a lot of sense. If one doesn't want to remove the
> generated files, that's what make distclean is for.
The fact that "autoreconf -i" does its job
Trevor Harmon writes:
> On Apr 28, 2010, at 6:27 AM, Peter Johansson wrote:
>> Of note, GCS states that: "More generally, ‘make maintainer-clean’
>> should not delete anything that needs to exist in order to run
>> configure and then begin to build the program".
> Yes, but that rule of thumb is
10 matches
Mail list logo
