civil-devel Mailing List for Civil

Nice.

Doubt there's anything to lose by trying to get the free OS license. :)



On 23 Oct 2004, at 18:01, Jan Ekholm wrote:

>
> A fairly interesting installer for Win and Lin:
>
> 	http://www.bitrock.com/
>
> -- 
>  The Emperor had all the qualifications for a corpse except, as it 
> were, the
>          most vital one.
>                                        -- Terry Pratchett, Interesting 
> Times
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on 
> ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give 
> us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Civil-devel mailing list
> Civ...@li...
> https://lists.sourceforge.net/lists/listinfo/civil-devel
>

A fairly interesting installer for Win and Lin:

	http://www.bitrock.com/

-- 
 The Emperor had all the qualifications for a corpse except, as it were, the
         most vital one.
                                       -- Terry Pratchett, Interesting Times

> So it would've worked just fine from the same directory where you 
> unpacked
> it all? As there is no way to get an universal installer and distutils
> falls a bit short, I think that just unpacking the Civil source package
> and compiling the C files should be enough. Distutils can do the
> compilation though.

Yeah, thinking about it, if I'd not run distutils it would have worked 
straight from the cvs checkout. Bar the compile needed.

> Hm, it may actually not do the civil directory at all...

I checked, it doesn't.

> Not used Python on Win32 for a few years, so I'm not sure of what works
> there, but I'd say that anything that can be done for Linux can also be
> done for the Windows side.

Moot point if neither of us will touch it?! ;)

Actually, I do have an IBM ThinkPad at work. Might be worth finding 
python and pygame and giving it a go...

G

On Tue, 12 Oct 2004, Gareth Noyce wrote:

>> You mean the installation actually worked for you? At least on Linux
>> there
>
>No, not at all. :(
>
>I just created a new directory, threw the src etc directories in there,
>compiled the c extension and edited properties.py - took a bit of
>fiddling was all.

So it would've worked just fine from the same directory where you unpacked
it all? As there is no way to get an universal installer and distutils
falls a bit short, I think that just unpacking the Civil source package
and compiling the C files should be enough. Distutils can do the
compilation though.

>> is still the matter with the binaries, where should they go? Other than
>> that I think most stuff should get installed just fine in
>> /usr/lib/python/site-packages/civil/. Alternatively the installer could
>
>Yeah, I'll need to check what I did, as setup.py didn't bother making
>the civil directory. I also dunno if that's on the default OS X path -
>not that it matters if I can work out how the app bundle stuff does its
>thing.

Hm, it may actually not do the civil directory at all...

>Speaking of which, I've got an application bundle running arbitrary
>python scripts. It's just normal #! /usr/bin/python stuff, but in a
>specific directory structure.
>
>Unfortunately, on the Mac there's a python for the terminal, and one
>for anything that needs the window manager (pythonw). I've no idea why
>this is the case, but my little app bundle hack doesn't seem to work
>with pythonw. Still trying to work this out atm...
>
>There's an app bundler thing as well, which I can try, but it puts all
>the frameworks and stuff in the application as well, which would mean a
>massive download. I'd rather that wasn't part of Civil's dist, tbh...
>
>> instead of copying files create them? Or instead of binaries in
>> /usr/bin/
>> or /usr/games/ just create suitable .desktop files in the proper
>> directory
>> (I think /usr/share/applications/games/, or something like that). The
>> .desktop file could specify a line like this as the executable:
>>
>> Exec=python -c "import civil....; civil.main()"
>>
>> For Windows there is probably something similar that could be created?
>
>For win32 I'd be tempted to dish out a py2exe'd up version? I'm not
>sure what the defaults for that machine are these days, been so long
>since I did any work on them.

Not used Python on Win32 for a few years, so I'm not sure of what works
there, but I'd say that anything that can be done for Linux can also be
done for the Windows side.

-- 

             Gravity is a habit that is hard to shake off.
                                              -- Terry Pratchett, Small Gods

> You mean the installation actually worked for you? At least on Linux 
> there

No, not at all. :(

I just created a new directory, threw the src etc directories in there, 
compiled the c extension and edited properties.py - took a bit of 
fiddling was all.

> is still the matter with the binaries, where should they go? Other than
> that I think most stuff should get installed just fine in
> /usr/lib/python/site-packages/civil/. Alternatively the installer could

Yeah, I'll need to check what I did, as setup.py didn't bother making 
the civil directory. I also dunno if that's on the default OS X path - 
not that it matters if I can work out how the app bundle stuff does its 
thing.

Speaking of which, I've got an application bundle running arbitrary 
python scripts. It's just normal #! /usr/bin/python stuff, but in a 
specific directory structure.

Unfortunately, on the Mac there's a python for the terminal, and one 
for anything that needs the window manager (pythonw). I've no idea why 
this is the case, but my little app bundle hack doesn't seem to work 
with pythonw. Still trying to work this out atm...

There's an app bundler thing as well, which I can try, but it puts all 
the frameworks and stuff in the application as well, which would mean a 
massive download. I'd rather that wasn't part of Civil's dist, tbh...

> instead of copying files create them? Or instead of binaries in 
> /usr/bin/
> or /usr/games/ just create suitable .desktop files in the proper 
> directory
> (I think /usr/share/applications/games/, or something like that). The
> .desktop file could specify a line like this as the executable:
>
> Exec=python -c "import civil....; civil.main()"
>
> For Windows there is probably something similar that could be created?

For win32 I'd be tempted to dish out a py2exe'd up version? I'm not 
sure what the defaults for that machine are these days, been so long 
since I did any work on them.

G

On Fri, 8 Oct 2004, Gareth Noyce wrote:

>was exactly what it should have been, and not changed as I thought :D

You mean the installation actually worked for you? At least on Linux there
is still the matter with the binaries, where should they go? Other than
that I think most stuff should get installed just fine in
/usr/lib/python/site-packages/civil/. Alternatively the installer could
instead of copying files create them? Or instead of binaries in /usr/bin/
or /usr/games/ just create suitable .desktop files in the proper directory
(I think /usr/share/applications/games/, or something like that). The
.desktop file could specify a line like this as the executable:

Exec=python -c "import civil....; civil.main()"

For Windows there is probably something similar that could be created?

-- 

 He says gods like to see an atheist around. Gives them something to aim at.
                                            -- Terry Pratchett, Small Gods

was exactly what it should have been, and not changed as I thought :D

Thanks

G

Trying to get this close to running. What's the state of the distutils 
stuff in CVS atm? Dodgy?

On my lappy it does a lot of copying/moving, but doesn't leave me with 
a working civil. Half the files are in my Framework/Versions/2.3/ 
folder, the other half in a build/ folder.

So, next question, what's the directory layout that I'm aiming for? 
I'll do it all by hand, edit properties.py etc, and get the beastie up 
and running, then I can see about moving it all to an app bundle (cos I 
really think I've figured out how to do it reliably... :)

Cheers

G

Just noticed; Looks like there's a distutils extension for OS X that'll 
do the .app bundle, which would be handy. Not had a chance to play with 
it yet, will report back :)

G

On 18 Sep 2004, at 09:21, Jan Ekholm wrote:

> On Fri, 17 Sep 2004, Marcus Alanen wrote:
>
>> On Fri, 17 Sep 2004, Jan Ekholm wrote:
>>
>>> A package does not mean that it couldn't all be installed in, say,
>>> /opt/civil/ or /usr/local/civil/... It would just mean that a 
>>> package is
>>> basically the tar.gz unpacked in some specified location (like 
>>> /opt/).
>>> Should be quite easy to actually do. Maybe optionally use convenience
>>> shell scripts in /usr/bin/ or similar.
>>
>> Hm. Yeswell. I think your last line is important. Basically you say
>> "maybe do something extra" which to me sounds like a build system, of
>> some kind, and of some simplicity. So I don't have anything against
>> works-out-of-the-box, but I do think we'll need
>> makefiles/autoconf and whatnot for the "convenience shell scripts".
>
> I'm not sure sure about that. A "convenience shell script" doesn't 
> have to
> be more than:
>
> #! /bin/sh
> cd /opt/civil/src && ./civil.py
>
> Or why not do them in Python as well?
>
> -- 
>           "Yes, bugger all that." said Nanny. "Let's curse somebody."
>                                             -- Terry Pratchett, Wyrd 
> Sisters
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Civil-devel mailing list
> Civ...@li...
> https://lists.sourceforge.net/lists/listinfo/civil-devel
>