Re: [Fink-devel] refactoring and documenting the Perl Fink:: classes and fink tool
On Sunday, December 1, 2002, at 12:05 AM, Benjamin Reed wrote: 1) is anyone already planning this? Not that I'm aware of... It would be nice to abstract the package management side of things away from the fink tool, definitely. It would be very helpful if anybody, say, wanted to write a different frontend using CamelBones. -- Finlay --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] refactoring and documenting the Perl Fink:: classes and fink tool
On Sunday, December 1, 2002, at 11:23 PM, Randal L. Schwartz wrote: Ben Er, we already do have a fink cleanup command. :) No we don't: Common commmands: [snip list without cleanup] This is from fink --help. If it's not there, it DOESN'T EXIST. Hmm, look at the header for that list Common commands, it does not say every command, there is no need to shout at the entire list. Sure there is lots of work to be done in all kinds of areas and your help is much appreciated, now please stop shouting and get working :-) Peter --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] refactoring and documenting the Perl Fink:: classes and fink tool
Peter == Peter O'Gorman [EMAIL PROTECTED] writes:
Peter Hmm, look at the header for that list Common commands, it does not
Peter say every command, there is no need to shout at the entire list.
And where do you find any other documentation then?
man fink = no indication of clean either.
Are you saying that man fink lists only common commands as well?
{sigh}
So, I'm not arguing with you. I think I'm pointing out how the state of
this vital hack we all have come know as fink.
It needs to be brought back from being bailing wire and scotch tape
into a good solid product. I'm willing to work on it.
But I also resent being told that I could have known about something
that wasn't documented. Please pay attention to the drift of my
message. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
[EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] refactoring and documenting the Perl Fink:: classes and fink tool
Last week, I tried to write a quick utility that would preen the cruft
from my /sw/src directory. You know, those distros that are no longer
needed. I thought no problem... a simple Perl script accessing the
Fink::* classes will suffice.
I was wrong. After about a dozen false starts, I still don't have a
working program. The classes are underdocumented, and the ones I
figured out by example seem to have hidden dependencies, either on
initialization, or needing to be run as root. (Why does something
that only wants to *look* at things need to be root?)
Out of my frustration, I gave up.
Since I know a little about Perl {grin}, and fink has made my world
rock, I'd like to rewrite the fink perl tool by refactoring the
classes and command utility in a more documented, tested, and reusable
way, as my way of contributing back to the fink project. My plan
would be to create Test::More-based object-oriented modules so that
regression tests can be run to assist with future maintainence and
debugging.
1) is anyone already planning this?
2) does anyone else share my pain?
3) if I take this on, who of you might want to help me?
Respond to the list or to me. Thanks.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
[EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
---
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] refactoring and documenting the Perl Fink:: classes and fink tool
On Saturday, November 30, 2002, at 06:36 PM, Randal L. Schwartz wrote: 1) is anyone already planning this? Not that I'm aware of... 2) does anyone else share my pain? Oh dear god yes! 3) if I take this on, who of you might want to help me? I'd be interested in helpping. I don't know how much time Max has, but I'm sure he'd be available at least for questions and so on. --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] refactoring and documenting the Perl Fink:: classes and fink tool
On Saturday, November 30, 2002, at 03:36 PM, Randal L. Schwartz wrote: Last week, I tried to write a quick utility that would preen the cruft from my /sw/src directory. You know, those distros that are no longer needed. I thought no problem... a simple Perl script accessing the Fink::* classes will suffice. Er, we already do have a fink cleanup command. :) Engine.pm - cmd_cleanup. Not to say a refactoring/documentation wouldn't be useful, but in this case what you wanted is already there.. -Ben --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
