I'm working on this stdeb configuration, It's really a nice tool !
Build can be configured in* setup.cfg file under a [sdist_dsc]* section.
For exemple, integration of a desktop file is very easy with this option :
> [sdist_dsc]
> MIME-Desktop-Files = leo.desktop
>
And then create a leo.desktop f
Hi,
I found a very nice python module that will do, I think, exactly what we
need : https://github.com/astraw/stdeb
For a first basic try I, just do this :
pip install stdeb
Then go into leo folder and run :
python setup.py --command-packages=stdeb.command bdist_deb
Then you get a nice pyth
fpm looks like a critical part of a toolchain. One script would put it
together, I think. Some further research is required, but it should be
pretty easy to build. We need a list of dependencies, a .desktop file and
some planning around paths. :-) But then it should be a simple matter of
runnin
I've downloaded the .deb and installed it via Ubuntu Software center.
Sounds that it doesn't like the "quality" of your "untrusted" package ;).
However that's a good start and the usefull files are copied into
/opt/leo-editor/leo-editor/leo/ which is probably too much folders...
One more things is
On 11/17/2014 6:33 PM, Chris George wrote:
Heh. The deb file includes the hidden directories. .git contains
121.5MB of stuff. Correcting now.
.git is a hidden killer. Tell your friends!
On Monday, November 17, 2014 3:24:39 PM UTC-8, Chris George wrote:
Good question. All I did was c
The new deb file is 7.1MB and has been uploaded.
Now if someone could test it...
https://www.wuala.com/technatica/Documents/temp/?key=8LhJkZwO0Rp1
On Monday, November 17, 2014 3:33:18 PM UTC-8, Chris George wrote:
>
> Heh. The deb file includes the hidden directories. .git contains 121.5MB
> of
Heh. The deb file includes the hidden directories. .git contains 121.5MB of
stuff. Correcting now.
On Monday, November 17, 2014 3:24:39 PM UTC-8, Chris George wrote:
>
> Good question. All I did was copy my leo-editor folder (which I recently
> installed via git) to /opt/leo-editor and run the
Good question. All I did was copy my leo-editor folder (which I recently
installed via git) to /opt/leo-editor and run the script. The leo-editor
folder checks in at 150.9MB.
I will try again with a fresh git install.
Chris
On Monday, November 17, 2014 3:02:18 PM UTC-8, Matt Wilkie wrote:
>
>
On Mon, Nov 17, 2014 at 1:55 PM, Chris George wrote:
> I jumped the gun. Apparently it takes while to upload 128.1MB.
Why so big? the source Leo distrib for pypi.org is ~6mb.
-matt
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscri
On Mon, Nov 17, 2014 at 3:19 PM, Matt Wilkie wrote:
> Forgot to say: 5.0b2 is published on PyPi!
>
Super! Thanks for the detailed instructions. I'll look at them closely
tomorrow.
EKR
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsub
This is a simple build of a deb, just the files, no dependencies. I can see
how it would be simple to set-up a script to build this dynamically.
Chris
On Monday, November 17, 2014 1:56:32 PM UTC-8, Chris George wrote:
>
> It is uploaded and appears in my other browser just fine.
>
> Chris
>
> On
It is uploaded and appears in my other browser just fine.
Chris
On Monday, November 17, 2014 1:49:54 PM UTC-8, Terry Brown wrote:
>
> On Mon, 17 Nov 2014 13:41:36 -0800 (PST)
> Chris George > wrote:
>
> > I have built a deb file from the latest git pull. Can anyone test it?
> > I use Chakra as
I jumped the gun. Apparently it takes while to upload 128.1MB.
On Monday, November 17, 2014 1:49:54 PM UTC-8, Terry Brown wrote:
>
> On Mon, 17 Nov 2014 13:41:36 -0800 (PST)
> Chris George > wrote:
>
> > I have built a deb file from the latest git pull. Can anyone test it?
> > I use Chakra as
On Mon, 17 Nov 2014 13:41:36 -0800 (PST)
Chris George wrote:
> I have built a deb file from the latest git pull. Can anyone test it?
> I use Chakra as a distribution, which doesn't use deb or rpm.
>
> https://www.wuala.com/technatica/Documents/temp/?key=8LhJkZwO0Rp1
>
Clicking on that link too
I have built a deb file from the latest git pull. Can anyone test it? I use
Chakra as a distribution, which doesn't use deb or rpm.
https://www.wuala.com/technatica/Documents/temp/?key=8LhJkZwO0Rp1
On Monday, November 17, 2014 1:02:58 PM UTC-8, Chris George wrote:
>
> This tool will likely sav
Forgot to say: 5.0b2 is published on PyPi!
-matt
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group,
On Mon, Nov 17, 2014 at 1:04 PM, Matt Wilkie wrote:
> python setup.py sdist upload
This is the tricky part, there's a bunch of prep-work that's hidden,
involving getting a properly formatted ~/.pypirc. It looks very
straightforward, according to docs, but in practice I've found devilishly
diff
Here's my workflow (written here as a script, but really done in fits and
starts):
*:: checkout tagged release & build package*
pushd b:\apps\leo-editor
git checkout tags/Leo-5.0-b2
python setup.py sdist
popd
*:: install from built package*
pip uninstall leo
pip install b:\apps\dist\leo-5.0b2.zi
This tool will likely save time. It can start with a directory and build
rpm, deb and even pkg files for Mac.
https://github.com/jordansissel/fpm
I will install it later and poke around to see how hard it is to build.
Chris
On Monday, November 17, 2014 5:31:38 AM UTC-8, Edward K. Ream wrote:
>
Not sure exactly what is involved...
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send e
Leo 5.0b2 is now available at:
http://sourceforge.net/projects/leo/files/Leo/
This release fixes several installation issues and updates installation
instructions for Linux/Ubuntu.
Afaik, this is the first time setup.py works as both a stand-alone script
and for use with pip install.
Please r
On Mon, Nov 17, 2014 at 1:39 PM, Edward K. Ream wrote:
>
Based on this, I think we are ready to move forward.
Matt's rev 07dfab8 (adding .json files to a list) sneaked in under the
wire. Thanks for this.
Edward
--
You received this message because you are subscribed to the Google Groups
On Mon, Nov 17, 2014 at 1:44 PM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
> On Mon, 17 Nov 2014 13:29:53 -0600
> "Edward K. Ream" wrote:
>
>
> I think some people (a
>
> majority?) will stop reading at "to install Leo download git...".
>
That's the irony. Imo, it'
On Mon, 17 Nov 2014 13:29:53 -0600
"Edward K. Ream" wrote:
> On Mon, Nov 17, 2014 at 12:53 PM, Chris George
> wrote:
>
> >
> None of this really helps with installation on Linux, but it might
> provide some perspective.
>
> Thanks for this. The irony is that using git to grab the latest
>
On Mon, Nov 17, 2014 at 12:51 PM, Matt Wilkie wrote:
>
> On Mon, Nov 17, 2014 at 9:30 AM, Edward K. Ream
> wrote:
>
>>
>> 1. pip install uses setup.py.
>>
>
> yes.
>
>
>> 2. It's not clear whether python setup.py install *also* works, or
>> *never* works, or something in between.
>>
>
>
> They b
On Mon, Nov 17, 2014 at 12:41 PM, Matt Wilkie wrote:
>
> Ideally we'd have someone to create .deb, .rpm etc.
>
In the past Ville Vainio has created these.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group a
On Mon, Nov 17, 2014 at 12:53 PM, Chris George wrote:
>
None of this really helps with installation on Linux, but it might provide
some perspective.
Thanks for this. The irony is that using git to grab the latest version
and a script to execute seems to be the easiest way *by far* to use Le
On Mon, Nov 17, 2014 at 12:04 PM, Kent Tenney wrote:
> Working great!
>
You're welcome. Thanks for the confirmation.
Edwardy
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, se
I am a full time Linux user and can only add my experience.
On installation of a new distribution on my computer, I install the
prerequisites (python, pyQt, enchant, docutils) using the package manager,
which varies with distribution. Then I run the following from a command
prompt:
git clone h
On Mon, Nov 17, 2014 at 9:30 AM, Edward K. Ream wrote:
>
> 1. pip install uses setup.py.
>
yes.
> 2. It's not clear whether python setup.py install *also* works, or *never*
> works, or something in between.
>
They both work -- on Windows; haven't tested Linux.
Up until a few weeks ago "pyth
>
> I understand there may be issues resulting from "sudo pip" to manage
> system packages instead of the system package manager
>
Ideally we'd have someone to create .deb, .rpm etc. but there's no one
around, at present, with those skills and motivation. << job ad here
:grin: >>
-matt
--
You
I'm only a sometime Linux user, so take comments below with that in mind.
- if user have root access and want to make leo available for all users
>
"sudo pip install ..." should work to install modules globally, and "pip
install --user ..." for just current user.
I understand there may be issue
Working great!
Thanks,
Kent
On Mon, Nov 17, 2014 at 11:27 AM, Edward K. Ream wrote:
> On Mon, Nov 17, 2014 at 11:16 AM, Edward K. Ream
> wrote:
>>
>> On Mon, Nov 17, 2014 at 10:56 AM, Kent Tenney wrote:
>>>
>>> > but it's hard to imagine that removing *trailing* whitespace would ever
>>> > be
On Mon, Nov 17, 2014 at 11:24 AM, Matt Wilkie wrote:
>
> Excellent. I'll release b2 today. Many thanks for your help.
>>
>
> I'm happy to have found a small corner where I can do something. Most of
> Leo dev has my head spinning. ;)
>
Well, installation issues make my head spin.
To recap my
On Mon, Nov 17, 2014 at 11:16 AM, Edward K. Ream
wrote:
> On Mon, Nov 17, 2014 at 10:56 AM, Kent Tenney wrote:
>
>> > but it's hard to imagine that removing *trailing* whitespace would ever
>> be dangerous.
>>
>> Indeed. In fact, I would use clean-all-lines as part of
>> routine housekeeping if
> Excellent. I'll release b2 today. Many thanks for your help.
>
I'm happy to have found a small corner where I can do something. Most of
Leo dev has my head spinning. ;)
> Is setup.py the only script involved? If not, I would like to make any
> other script a script button in leoDist.leo.
>
On Mon, Nov 17, 2014 at 10:56 AM, Kent Tenney wrote:
> > but it's hard to imagine that removing *trailing* whitespace would ever
> be dangerous.
>
> Indeed. In fact, I would use clean-all-lines as part of
> routine housekeeping if it removed trailing whitespace.
>
I'll do this asap.
Edward
--
> but it's hard to imagine that removing *trailing* whitespace would ever be
> dangerous.
Indeed. In fact, I would use clean-all-lines as part of
routine housekeeping if it removed trailing whitespace.
Leading whitespace (aka indentation) is another matter ...
On Mon, Nov 17, 2014 at 10:45 AM,
On Mon, Nov 17, 2014 at 9:22 AM, Steve Butterworth <
steven.butterwo...@gmail.com> wrote:
> On Saturday, 15 November 2014 10:21:23 UTC-5, Edward K. Ream wrote:
>
>> Ahem. This is a much trickier problem than it may at first appear. I
>> can assure you that we take this problem seriously.
>>
>
>
On Mon, Nov 17, 2014 at 8:21 AM, Davy Cottet wrote:
> From, the earlier discussion I understood that pip installation was
> better...
> But I think it may change based on various factors :
>
Thanks for these comments :-)
Edward
--
You received this message because you are subscribed to the G
On Mon, Nov 17, 2014 at 7:31 AM, Edward K. Ream wrote:
> The present install.txt recommends running the install script with sudo
> ./install (See the P.S.).
>
> But the install script no longer exists at the top level. What should the
> docs say? That is, what is the easiest way to install on L
On Mon, Nov 17, 2014 at 8:26 AM, Kent Tenney wrote:
> Update on @auto myfile.md
>
> If the trailing whitespace is removed, reload from disk is happy.
>
Good.
>
> So, if clean-all-lines cleaned trailing whitespace (which I would
> expect it is meant to) things would be much better.
>
> Would
On Saturday, 15 November 2014 10:21:23 UTC-5, Edward K. Ream wrote:
> Ahem. This is a much trickier problem than it may at first appear. I
> can assure you that we take this problem seriously.
>
My apologies for implying that it was simple. It was actually the fact that
`python setup.py inst
Update on @auto myfile.md
The current import error can be duplicated by placing
whitespace before the newline, reload from disk fails
because the importer correctly removed the trailing whitespace.
The log suggests clean-all-lines command might fix it.
running clean-all-lines reports
cleaned 0 n
From, the earlier discussion I understood that pip installation was
better...
But I think it may change based on various factors :
- if user have root access and want to make leo available for all users
- if user want development or stable version :
- if user can and want to install it with pip
On Mon, Nov 17, 2014 at 8:02 AM, Davy Cottet wrote:
> For a general point of vue, I think it may change depending on the
> following elements :
>
Did you hit "send" too soon?
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscri
For a general point of vue, I think it may change depending on the
following elements :
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@go
The present install.txt recommends running the install script with sudo
./install (See the P.S.).
But the install script no longer exists at the top level. What should the
docs say? That is, what is the easiest way to install on Linux?
Edward
P.S. Here is the part of install.txt relating to
On Monday, November 17, 2014 7:14:30 AM UTC-6, Davy Cottet wrote:
>
> Yes it is, thanks !
>
> I guess it may be a basic python trick... but could you tell me the
> difference between that and what I did before :
>
> def mymakecommand(keywords,builder):
> make(builder)
>
> builder is no
Yes it is, thanks !
I guess it may be a basic python trick... but could you tell me the
difference between that and what I did before :
def mymakecommand(keywords,builder):
make(builder)
and
def mymakecommand(keywords,builder=builder):
make(builder)
--
You received t
Thanks!
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegrou
On Mon, Nov 17, 2014 at 4:14 AM, Davy Cottet wrote:
>
> Now, how do I declare a new command for every builder ?
>
> I've tr
> i
> ed this :
>
>
>
> table = []
> for builder in builders:
> @g.command('make-'+builder)
>
>
> def mymakecommand(keywords):
>
>
> make(builder)
>
On Mon, Nov 17, 2014 at 12:07 AM, Matt Wilkie wrote:
> I think we're good to go now.
>
Excellent. I'll release b2 today. Many thanks for your help.
Is setup.py the only script involved? If not, I would like to make any
other script a script button in leoDist.leo.
Edward
--
You received th
Hi,
I'm actually working on a Sphinx* plugin*.
*First why a plugin ? :*
Initially, I would like to implement Sphinx functionalities
(menus+commands) inside a standalone .leo template file.
The basic aim to create a 'Sphinx' menu with 'make' submenu and subitems
for every sphinx builders (make ht
54 matches
Mail list logo
