May 26, 2012
Dear,

dbuilder: https://github.com/dbuilder-developers/dbuilder

currently dbuilder works on Linux, Apple, Windows platform (at least)
this tool allow to us to build easily lib, or desktop application
It support // build, // install
i think i will improve this tool to be use as a package manager, for
this add to supported config file a new section
---
[[dependenies]]
[[[xxx]
version_type=[version, tag, revision]
repo_url=https://github ...https://bitbucket ...
tool=[git, hg, svn]
version=xx
tag=xx
revision=xx
---

put the config file at root of repo for detect this file and use it

if this config is not enough for to be used as config said to me what need to be added

anyone is welcome

May 26, 2012
On 2012-05-26 13:34, bioinfornatics wrote:
> Dear,
>
> dbuilder: https://github.com/dbuilder-developers/dbuilder
>
> currently dbuilder works on Linux, Apple, Windows platform (at least)
> this tool allow to us to build easily lib, or desktop application
> It support // build, // install
> i think i will improve this tool to be use as a package manager, for
> this add to supported config file a new section
> ---
> [[dependenies]]
> [[[xxx]
> version_type=[version, tag, revision]
> repo_url=https://github ...https://bitbucket ...
> tool=[git, hg, svn]
> version=xx
> tag=xx
> revision=xx
> ---
>
> put the config file at root of repo for detect this file and use it
>
> if this config is not enough for to be used as config said to me what
> need to be added
>
> anyone is welcome

I don't think a built tool and package manager should be in the same tool. A built tool works with individual files. A package manager works with package, i.e. complete libraries/tools/applications.

I also think that in the long run both a build tool and a package manager needs to use a full programming language as their config files.

-- 
/Jacob Carlborg
May 26, 2012
Le samedi 26 mai 2012 à 17:33 +0200, Jacob Carlborg a écrit :
> On 2012-05-26 13:34, bioinfornatics wrote:
> > Dear,
> >
> > dbuilder: https://github.com/dbuilder-developers/dbuilder
> >
> > currently dbuilder works on Linux, Apple, Windows platform (at least)
> > this tool allow to us to build easily lib, or desktop application
> > It support // build, // install
> > i think i will improve this tool to be use as a package manager, for
> > this add to supported config file a new section
> > ---
> > [[dependenies]]
> > [[[xxx]
> > version_type=[version, tag, revision]
> > repo_url=https://github ...https://bitbucket ...
> > tool=[git, hg, svn]
> > version=xx
> > tag=xx
> > revision=xx
> > ---
> >
> > put the config file at root of repo for detect this file and use it
> >
> > if this config is not enough for to be used as config said to me what need to be added
> >
> > anyone is welcome
> 
> I don't think a built tool and package manager should be in the same tool. A built tool works with individual files. A package manager works with package, i.e. complete libraries/tools/applications.
> 
> I also think that in the long run both a build tool and a package manager needs to use a full programming language as their config files.
> 

pypy from python do both http://pypy.org/ get dependencies, build from setup script

May 26, 2012
Fix link: http://pypi.python.org/pypi that is pypi and not pypy

May 27, 2012
On Saturday, 26 May 2012 at 15:33:27 UTC, Jacob Carlborg wrote:
> On 2012-05-26 13:34, bioinfornatics wrote:
>> Dear,
>>
>> dbuilder: https://github.com/dbuilder-developers/dbuilder
>>
>> currently dbuilder works on Linux, Apple, Windows platform (at least)
>> this tool allow to us to build easily lib, or desktop application
>> It support // build, // install
>> i think i will improve this tool to be use as a package manager, for
>> this add to supported config file a new section
>> ---
>> [[dependenies]]
>> [[[xxx]
>> version_type=[version, tag, revision]
>> repo_url=https://github ...https://bitbucket ...
>> tool=[git, hg, svn]
>> version=xx
>> tag=xx
>> revision=xx
>> ---
>>
>> put the config file at root of repo for detect this file and use it
>>
>> if this config is not enough for to be used as config said to me what
>> need to be added
>>
>> anyone is welcome
>
> I don't think a built tool and package manager should be in the same tool. A built tool works with individual files. A package manager works with package, i.e. complete libraries/tools/applications.
>
> I also think that in the long run both a build tool and a package manager needs to use a full programming language as their config files.


Yes they should be separate tools but that's doesn't mean they can't work together.

Let's say you have a build configuration file and an package manager configuration file in the same folder. When you call the build process, if the dependencies aren't there, it calls the package manager to fetch all your dependencies and then it adds the required include and lib path in your build configuration. Adding an dependency to your project is now easier and doesn't require manual management.


May 27, 2012
On 2012-05-26 19:40, bioinfornatics wrote:

> pypy from python do both http://pypy.org/ get dependencies, build from
> setup script

What does a python tool need to build, external libraries?

In comparison Rubygems and Rake are to separate tools.

-- 
/Jacob Carlborg
May 27, 2012
On 2012-05-27 03:22, "Michaël Larouche" <michael.larouche@gmail.com>"
>
> Yes they should be separate tools but that's doesn't mean they can't
> work together.

Of course they should work together.

-- 
/Jacob Carlborg
May 27, 2012
Am 26.05.2012 19:42, schrieb bioinfornatics:
>
> Fix link: http://pypi.python.org/pypi that is pypi and not pypy
>

Wrong it's PIP, http://pypi.python.org/pypi/pip/1.1
PyPi is just the index.
May 27, 2012
On Sun, 2012-05-27 at 12:18 +0200, Jacob Carlborg wrote:
> On 2012-05-26 19:40, bioinfornatics wrote:
> 
> > pypy from python do both http://pypy.org/ get dependencies, build from setup script
> 
> What does a python tool need to build, external libraries?
> 
> In comparison Rubygems and Rake are to separate tools.

pip (and easy_install) are package downloaders and installers, invoke bytecode generation of the installed, they are not build tools.  The offerings for build tools from the Python arena are SCons and Waf.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


May 27, 2012
On Sun, 2012-05-27 at 13:33 +0100, Russel Winder wrote:

> pip (and easy_install) are package downloaders and installers, invoke bytecode generation of the installed, they are not build tools.  The offerings for build tools from the Python arena are SCons and Waf.

I guess I should have added that because C and C++ can be used to realize CPython PVM extensions, Python package installers have to know how to compile C and C++ code to shared objects / dynamically linked libraries.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


Top | Discussion index | About this forum | D home