Am Die, den 18.11.2003 schrieb Branden Robinson um 22:53: > [Please CC me on replies.] > > On Tue, Nov 18, 2003 at 06:13:53PM +0100, Gaudenz Steinlin wrote: > > Unfortunately I can not find the changelog in the pre 2.0.2 tarball on > > the progeny website. Where can I find it? > > Sorry about that. A (compressed) comprehensive log is attached. Thanks. > > > I sent 2 sets of patches[1][2] to Jeff and Eric, which as far as I could > > see are not integrated in the snapshot and on which we had no feedback > > so far. > > I've opened tickets about these, and hope to have time to look at them > this week. > > The second one (support building without libcurl) may have been resolved > by Eric's recent changes. Please let me know if you're satisfied by > Eric's solution. What I'm missing is a option to "configure" to disable curl. It tries to autodetect curl and enables it if it's found. To really see how eric intended to build curl and non-curl versions in the same debian packet we need access to the debian dir (which is not included in the 2.0.2-pre tarball). :-( > > > Also petter sent a mail asking for the current status of the > > integration of discover2 into debian[3] which is unanswered until now. > > I think his questions were largely answered by the website announcement, > but if there are clarifications you'd like, please ask. > > > Additionally it would be nice to have a newer discover-data package. The > > newest I have found so far is about one year old and only contains very > > few usable entries for usb devices. > > Yes, the discover2 discover-data package needs to be resynced with the > many updates that have happened to discover1's data. Does progeny have any actualized xml files to test with for us? This would be great. > > > We would also be interested to know your plans on how to get discover2 > > into the debian archive. Are you planning to replace discover1 or will > > there be a new discover2 package. The debian-installer team would like > > to be able to have discover1 and 2 in parallel to be sure to have a > > working configuration while testing discover2. So please don't remove > > discover1. > > Well, here's what I'd personally like: :) > > 1) Get a good feedback cycle going between Progeny and debian-boot > regarding discover2's suitability for debian-installer. The goal > here is "feature-complete", not "bug-free". To decide if they are feature-complete we need debs and udebs representing the current status. As far as I'm concerned the only wishlist feature for discover not implemented is ieee1394 support. It would be great to be able to install to/from firewire media. Discover 2 seems to be feature complete to replace the functionality of discover1. While testing my self-built discover2 udebs the biggest problem was the lack of a decent hw-list. > 2) Hand off maintenance off Discover 1.x to the d-i team. You guys are > already the de facto maintainers of Discover 1.x and everyone who > reads the changelogs knows that. > 3) Rename the current discover source package to discover-old or > discover1; drop the libdiscover-dev package from it; rename the > discover package to discover-old or discover1, and have it Conflict: > discover. > 4) Thanks to 1), we will upload discover 2.0 to Debian unstable. This sounds OK to me. So we can rename discover to discover1 now and expect discover2 packages soon? Do the other d-i developers agree with this plan? > > That should make it clear that DIscover 1.x is deprecated, but will > enable either to be installable, and d-i can use either one, > transitioning on a schedule that is completely under your control. > > How does that sound? Good.
Thanks Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
