> So while your modification is great for all but the next-to-last step that
> a developer takes, it's not practical for most users of Fink, who want
> to go ahead and build the deb, or take a pre-built deb and install it.

For users of fink, I think the current setup is fine.  You're right, most
people just want to install the software and the assumption is that the
package maintainers have already taken care of these details.

The modification is aimed squarely at package maintainers, particularly
budding package maintainers.  If you're inclined to try to build software,
it should be as easy as possible to start making .info files so that
others can benefit from your work.  In particular it should be easy to
learn your way around .info file creation without fear of trashing your
system.

Anyway, I think it'd be ideal if one of two things happened:
1) The next version of fink include the command line option
--package-maintainer-mode so that:
fink --package-maintainer-mode rebuild package
doesn't try to become root, goes through the whole build process, skips
.deb creation, and leaves the /sw/src/root-package directory for
inspection.

2) Or, add to the top of the "Package maintainer docs" a paragraph that
describes how to achieve "safe" package tests by commenting the relevant
line in Engine.pm and making /sw/src writeable by users.

Or, maybe this doesn't matter since people who are likely to try to build
.info files are also likely to be able to figure out how to make fink
behave the way they want.  Making the information easily accessible would
just save a little work.

Cheers,
Greg


-------------------------------------------------------
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

Reply via email to