it is good to work in CVS. But for major dep engine changes you might want to work in a 'branch' instead, not HEAD.

-Ben

On Dec 2, 2003, at 7:22 PM, TheSin wrote:

I'm just gonna do it steps, first I need BuildConflicts, which I just added, now I'm gonna add the transparent check before every build code, it'll remove and install as needed but won't ask since the first summary will cover it all anyhow. And I've got that part almost working already, but I need to make small commits in between to not confuse myself, and so other can't help find any problems if there are any in little burst as so I don't get too far ahead, but this stuff has been put off too long, and been complained about too much. So instead of my complaining about it again I just decided to do it.

---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.

On 2-Dec-03, at 4:23 PM, Max Horn wrote:

I think doing this properly is a very hard task. Are you sure you're up to it? For now, it might be *much* simpler to simply change "fink remove" to use "apt-get remove" instead of "dpkg --remove". That will give you almost exactly the functionality you want w/o having to study graph theory.



------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to