pkgsrc-WIP-discuss archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: jdk request
- To: walt <wa1ter%myrealbox.com@localhost>
- Subject: Re: jdk request
- From: Geert Hendrickx <geert.hendrickx%ua.ac.be@localhost>
- Date: Sat, 20 Aug 2005 01:52:56 +0200 See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 1.0 FORGED_RCVD_HELO Received: contains a forged HELO 0.0 AWL AWL: From: address is in the auto white-list
On Tue, Aug 16, 2005 at 03:01:35PM -0700, walt wrote:
> Hi Geert,
>
> Thanks for getting the jdk14 package working again -- very good work!
>
> I know you decided to revert to the eyesbeyond patchset number 7 to make
> your job easier, and that choice payed off well. The one big downside to
> that choice is that the 'experimental' patchset had support for
> DragonFlyBSD, but patchset 7 does not.
>
> Now that the jdk is working well, would you be willing to go back and get
> the 'experimental' patchset working also? I just tried applying that
> patchset to your latest jdk14, and I got 1 out of 4 hunks to apply
> successfully. Just think of the pleasure you would get from fixing the
> other three hunks! :o)
>
> Thanks!
Sorry for the later reply -- just came back from vacation.
There was a very good reason to revert to a tagged version of the patchset:
the -current version changes, and not only the checksum gets outdated then,
also the patches must be "re-diffed" (and sometimes dropped).
If there is a good reason to track -current (and Dragonfly support looks
like a good reason to me), I propose to split the jdk14 package into two
packages; a "stable" one tracking the tagged version of the patchset (now
7), and another one tracking the -current version (which should be updated
frequently then).
Another option, if it's only for the DragonflyBSD support, is to include
those (probably few) extra patches in patches/, and drop 'em if patchset-8
is tagged.
I would prefer the latter option, to minimize maintainance. We could even
add other patches in-current-but-not-in-7 to the patches/ dir, which keeps
the package working (correct checksum e.d.) at all times, but also adds
extra features from the current patchset. Thinking of it, this seems like
the best way to go to me, but please post your opinion on this.
GH
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss
Home |
Main Index |
Thread Index |
Old Index