[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Planning a 3.11 snap release
From: |
Hal Murray |
Subject: |
Re: [gpsd-dev] Planning a 3.11 snap release |
Date: |
Sun, 24 Nov 2013 10:24:34 -0800 |
address@hidden said:
> I think leapfetch should be removed from the *build* process entirely. It's
> certainly reasonable to have a "secondary fetch" step to freshen it, that
> can be run to commit a new file into git, or by someone who chooses to do
> that. If there are releases every 6 months, then this isn't that big a deal
> anyway.
I'd be happy with leapfetch being pulled out of mainline builds. Somebody
has to remember to run it occasionally. Perhaps a cron job, and/or move it
to over to making tarballs.
There is another reason for splitting the build step into two parts, one done
before making the tarball. You can use tools that may not be available on
the build systems. Obviously, this only works for things that don't actually
need to be "built" on the build system, but that covers a lot of
documentation and preprocessors like bison/yacc.
--
These are my opinions. I hate spam.
- [gpsd-dev] Planning a 3.11 snap release, Eric S. Raymond, 2013/11/24
- Re: [gpsd-dev] Planning a 3.11 snap release, Greg Troxel, 2013/11/24
- Re: [gpsd-dev] Planning a 3.11 snap release, Greg Troxel, 2013/11/26
- Re: [gpsd-dev] Planning a 3.11 snap release, Eric S. Raymond, 2013/11/26
- Re: [gpsd-dev] Planning a 3.11 snap release, Greg Troxel, 2013/11/26
- Re: [gpsd-dev] Planning a 3.11 snap release, Eric S. Raymond, 2013/11/26
- Re: [gpsd-dev] Planning a 3.11 snap release, Greg Troxel, 2013/11/26
- Re: [gpsd-dev] Planning a 3.11 snap release, Eric S. Raymond, 2013/11/26