Hi folks,
I think at this point we should probably be writing utilities outside
of newapkbuild (a la apkbuild-cpan), at least for those libraries &
applications which can be obtained from CPAN-like code stores. I think
this is particularly needful because newapkbuild is getting a bit on
the hefty side, and in any event, apkbuild-cpan can also be used
separately for added functionality.
--Kiyoshi Aman
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
On Jun 28, 2011, at 8:19 AM, Kiyoshi Aman <aphrael@alpinelinux.org> wrote:
> Hi folks,> > I think at this point we should probably be writing utilities outside> of newapkbuild (a la apkbuild-cpan), at least for those libraries &> applications which can be obtained from CPAN-like code stores. I think> this is particularly needful because newapkbuild is getting a bit on> the hefty side, and in any event, apkbuild-cpan can also be used> separately for added functionality.> > --Kiyoshi Aman
What about keeping apkbuild-cpan separate for when you want more advanced functionality but having an option to call it from within newapkbuild for basic usage like bumping versions and similar tasks?
Jeff
> > > ---> Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org> Help: alpine-devel+help@lists.alpinelinux.org> --->
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
On Mon, 27 Jun 2011 23:36:17 +0000
Fabian Affolter <fabian@affolter-engineering.ch> wrote:
> With -q ('-q' for the moment, please change that) a template> APKBUILD file for a python module is created. 'depends' and> 'makedepends' are filled with standard values.
Thanks!
I changed the -q to -y for now. I wonder if we should use -t <type>
instead: newapkbuild -t python ...
I also renamed config_* to build_* since this functions now also
includes the 'make' command if needed.
And i added a build_make() and package_make() in case there is only a
single Makefile.
While there I also moved the init.d script stuff since all kinds of
build types could have an init.d script, not only autotools.
Please test!
Thanks!
-nc
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
On Tue, 28 Jun 2011 09:06:47 -0400
Jeff Bilyk <jbilyk@gmail.com> wrote:
> > On Jun 28, 2011, at 8:19 AM, Kiyoshi Aman <aphrael@alpinelinux.org>> wrote:> > > Hi folks,> > > > I think at this point we should probably be writing utilities> > outside of newapkbuild (a la apkbuild-cpan), at least for those> > libraries & applications which can be obtained from CPAN-like code> > stores. I think this is particularly needful because newapkbuild is> > getting a bit on the hefty side, and in any event, apkbuild-cpan> > can also be used separately for added functionality.> > > > --Kiyoshi Aman> > What about keeping apkbuild-cpan separate for when you want more> advanced functionality but having an option to call it from within> newapkbuild for basic usage like bumping versions and similar tasks?
We could also have newapkbuild call apkbuild-cpan. apkbuild-cpan has
some extra stuff that helps keeping the apkbuild updated.
but for now, apkbuild-cpan works only with stuff that are in cpan.
newapkbuild can handle perl things that are not in cpan.
-nc
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---