Re: CVS commit: wip/awk-pkgsrc-dewey

[Tobias Nygren <tnn%NetBSD.org@localhost>]

On Mon, 18 Feb 2008 21:48:15 +0200
Aleksey Cheusov <cheusov%tut.by@localhost> wrote:

> 
>  >> Module name:      wip
>  >> Committed by:     cheusov
>  >> Date:             Mon Feb 18 09:20:19 UTC 2008
>  >> 
>  >> Added Files:
>  >>   wip/awk-pkgsrc-dewey: DESCR Makefile PLIST
>  >>   wip/awk-pkgsrc-dewey/files: Makefile Makefile.version
>  >>       pkgsrc-dewey.awk
>  >> 
>  >> Log Message:
>  >> awk dewey functions
> 
> > I'm not sure where you're going with this, but wouldn't it make sense
> > to roll all/some of the wip/pkg_* packages into one single package?
> 
> I meaningly separate them.
> wip/awk-pkgsrc-dewey implements dewey functions for awk
> (Yes, I reimplement yet another wheel here ;-) ).
> pkg_cmp_summary compares two summary files.
> pkg_cmp_update_summary and pkg_update_summary update
> source and binary summaries respectively.
> One program (package) - one function.
> This is a good style of design.
> All these programs are completely different.
> Based on wip/awk-pkgsrc-dewey and wip/runawk
> I have a plan to develop more tools for managing packages.
> What's wrong? What you worry about?

No problem, I was just curious about the long term plans for this.
Even if the programs have different use they can still be bundled
to ease maintenance burden. For example, we don't have separate packages
for pkg_add and pkg_info.

> > Something like wip/pkg_experimental
> Everything in wip is experimental. This is a "sandbox". Right?

Sure :-) hack away.

Take care,
-Tobias

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
pkgsrc-wip-cvs mailing list
pkgsrc-wip-cvs%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-cvs