external update-copyright package

BE folks,

I've recently realized that the `update_copyright.py` code should
really live outside of BE.  I've pulled it out as a stand-alone
package [1], and converted BE to use the updated version [2].  I also
cleaned up `release.py`, and added a `.mailmap`.

This makes the BE repository more focused, but adds an external
dependency for copyright updates.  You'll need to install my
update-copyright package if you:

* Want to run the copyright updates (i.e. you are me :p)
* Want to make a release from the versioned source (i.e. you are
  Chris, or you write live packages for a distribution)

If you don't mind copyright blurbs potentially being a few months out
of date, or missing a recent author or two, feel free to ignore this
message.

Cheers,
Trevor

[1]: http://blog.tremily.us/posts/update-copyright/
[2]: git://gitorious.org/~wking/be/wtk.git

--

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

Re: external update-copyright package

Hi Trevor,

On Thu, Feb 16 2012, W. Trevor King wrote:
> BE folks,
>
> I've recently realized that the `update_copyright.py` code should
> really live outside of BE.  I've pulled it out as a stand-alone
> package [1], and converted BE to use the updated version [2].  I also
> cleaned up `release.py`, and added a `.mailmap`.
>
> This makes the BE repository more focused, but adds an external
> dependency for copyright updates.  You'll need to install my
> update-copyright package if you:
>
> * Want to run the copyright updates (i.e. you are me :p)
> * Want to make a release from the versioned source (i.e. you are
>   Chris, or you write live packages for a distribution)
>
> If you don't mind copyright blurbs potentially being a few months out
> of date, or missing a recent author or two, feel free to ignore this
> message.
>
> Cheers,
> Trevor
>
> [1]: http://blog.tremily.us/posts/update-copyright/
> [2]: git://gitorious.org/~wking/be/wtk.git

Thanks.  It seems like a good use of a git submodule to me -- want to
try that?

pending merge requests on gitorious

I don't usually use the gitorious web interface, but I was just there
adding a new public key, and noticed that there are three open merge
requests listed for the main repository.  Leaving them out there
probably makes it more likely that others think we're dead, so here
are my suggestions for each request:

* http://gitorious.org/be/be/merge_requests/5
  This has been in the main repository since
    f0011cf09d1385f983853b1d11ae5573148139bb
  It should be marked "Merged" (or closed, accepted, etc.  I'm not
  sure what gitorious supports).

* http://gitorious.org/be/be/merge_requests/6
  Same as above.

* http://gitorious.org/be/be/merge_requests/7
  Niall made his initial post back in August last year [1], and we
  (Niall and I) discussed his patches in the September thread starting
  with [2].  As far as the merge request goes, I'm deferring until we
  switch to Python 3 with its built-in `distribute` module.  Niall
  doesn't seem to have updated his branch since August, but I think
  this request should be left open.

Cheers,
Trevor

[1]: http://void.printf.net/pipermail/be-devel/2011-August/000826.html
[2]: http://void.printf.net/pipermail/be-devel/2011-September/000838.html
--

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).

Re: external update-copyright package

On Thu, Feb 16, 2012 at 01:42:36PM -0500, Chris Ball wrote:
> It seems like a good use of a git submodule to me -- want to try
> that?

It should be working as a submodule now.

I've never really bought into the submodule idea.  Commit-level
binding seems a bit persnickety ;).  Maybe I'm just spoiled by having
a good package manager :p.  However, update-copyright will hopefully
have a very boring history (no more commits from now until the
end of time), so I'm OK with it in this case ;).

--

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

_______________________________________________
Be-devel mailing list
Be-devel <at> bugseverywhere.org
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

Re: external update-copyright package

Hi,

On Thu, Feb 16 2012, W. Trevor King wrote:
> I've never really bought into the submodule idea.  Commit-level
> binding seems a bit persnickety ;).  Maybe I'm just spoiled by having
> a good package manager :p.  However, update-copyright will hopefully
> have a very boring history (no more commits from now until the
> end of time), so I'm OK with it in this case ;).

Yep, agree on all counts -- I normally don't use submodules but figured
it should work here since the script won't be changing often.

I've merged your master branch into mainline now.

Thanks,

- Chris.
--

-- 
Chris Ball   <cjb <at> laptop.org>   <http://printf.net/>
One Laptop Per Child

Re: pending merge requests on gitorious

Hi,

On Thu, Feb 16 2012, W. Trevor King wrote:
> I don't usually use the gitorious web interface, but I was just there
> adding a new public key, and noticed that there are three open merge
> requests listed for the main repository.  Leaving them out there
> probably makes it more likely that others think we're dead, so here
> are my suggestions for each request:
>
> * http://gitorious.org/be/be/merge_requests/5
>   This has been in the main repository since
>     f0011cf09d1385f983853b1d11ae5573148139bb
>   It should be marked "Merged" (or closed, accepted, etc.  I'm not
>   sure what gitorious supports).
>
> * http://gitorious.org/be/be/merge_requests/6
>   Same as above.
>
> * http://gitorious.org/be/be/merge_requests/7
>   Niall made his initial post back in August last year [1], and we
>   (Niall and I) discussed his patches in the September thread starting
>   with [2].  As far as the merge request goes, I'm deferring until we
>   switch to Python 3 with its built-in `distribute` module.  Niall
>   doesn't seem to have updated his branch since August, but I think
>   this request should be left open.

Thanks, all done as above.

- Chris.
--

-- 

Re: pending merge requests on gitorious

On 16 Feb 2012 at 13:16, W. Trevor King wrote:

> * http://gitorious.org/be/be/merge_requests/7
>   Niall made his initial post back in August last year [1], and we
>   (Niall and I) discussed his patches in the September thread starting
>   with [2].  As far as the merge request goes, I'm deferring until we
>   switch to Python 3 with its built-in `distribute` module.  Niall
>   doesn't seem to have updated his branch since August, but I think
>   this request should be left open.

Yeah that thread just kinda hanged in the middle when we were 
discussing the Windows bug regarding default filesystem character 
encoding ...

I've been very busy writing an economics book which just went to the 
publisher today actually, so spare coding time has been very limited 
during recent months. I have found myself using BEurtle for some very 
crazy things, like in the GIT repo housing the book manuscript, so I 
have been living daily with its bugs and half baked UI decisions.

I've also had quite a few enquiries from some well known coders on 
the internet who are looking for a tool just like BEurtle, but 
BEurtle simply isn't fit for purpose yet. For example, it needs 
github and redmine issue tracking integration, and a GUI way of 
attaching files. Then it'll become very popular. I need all those 
things myself badly, so I'm highly motivated to fix these if just for 
my own workflow.

Regarding the merge, I would suggest merging the parts which are 
outside the distribute.py changes e.g. be.bat, !Generate_version.bat. 

Re: pending merge requests on gitorious

On Fri, Feb 17, 2012 at 12:03:11AM +0000, Niall Douglas wrote:
> Regarding the merge, I would suggest merging the parts which are 
> outside the distribute.py changes e.g. be.bat, !Generate_version.bat. 
> Then at least it works on Windows.

I confess that I have no MS Windows experience, but what is the
`BE_TOOL_ERRORLEVEL` bit doing in your `be.bat`?  It is not an
environmental variable used by BE.  Do you use it in BEurtle?

--

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

_______________________________________________
Be-devel mailing list
Be-devel <at> bugseverywhere.org
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

BE docs website

One last thing, while I'm cleaning up some packaging details.

If you have a Gentoo box, it's now easy to build the docs yourself by
setting the `doc` USE flag when emerging by `dev-util/be` package.

I've posted the HTML docs for current trunk on http://be.tremily.us/,
and I'll probably keep that pretty up to date as time goes on.
However, my upload bandwidth is fairly limited, so I'd appreciate
external mirroring (e.g. at docs.bugseverywhere.org, which I see is
getting on two years out of date :p).

A slow, monthly `wget` should be an acceptable mirroring method.

Trevorz

--

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

_______________________________________________
Be-devel mailing list
Be-devel <at> bugseverywhere.org
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

Re: BE docs website

Hi,

On Thu, Feb 16 2012, W. Trevor King wrote:
> One last thing, while I'm cleaning up some packaging details.
>
> If you have a Gentoo box, it's now easy to build the docs yourself by
> setting the `doc` USE flag when emerging by `dev-util/be` package.
>
> I've posted the HTML docs for current trunk on http://be.tremily.us/,
> and I'll probably keep that pretty up to date as time goes on.
> However, my upload bandwidth is fairly limited, so I'd appreciate
> external mirroring (e.g. at docs.bugseverywhere.org, which I see is
> getting on two years out of date :p).

Ouch, good point.  I've mirrored it at docs.bugseverywhere.org now;
I didn't set up automatic mirroring, though.

Thanks!

- Chris.
--

-- 
Chris Ball   <cjb <at> laptop.org>   <http://printf.net/>
One Laptop Per Child