
Hi, I believe the xhtml package is currently unmaintained. As it is something that used to be distributed with GHC, is it something that libraries@ could/should take on? Cheers, Ganesh

I am listed as the current maintainer, but I don't have any time to
work on it. Who would like to take over?
/Bjorn
On Sun, Mar 7, 2010 at 21:41, Ganesh Sittampalam
Hi,
I believe the xhtml package is currently unmaintained. As it is something that used to be distributed with GHC, is it something that libraries@ could/should take on?
Cheers,
Ganesh _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

Robin Bate Boerop
I am listed as the current maintainer, but I don't have any time to work on it. Who would like to take over?
/Bjorn
On Sun, Mar 7, 2010 at 21:41, Ganesh Sittampalam
wrote: Hi,
I believe the xhtml package is currently unmaintained. As it is something that used to be distributed with GHC, is it something that libraries@ could/should take on?
Cheers,
Ganesh _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

On Thu, Jul 29, 2010 at 07:18:23PM +0100, Bjorn Bringert wrote:
Robin Bate Boerop
is the only person to express interest in taking over xhtml. I hereby hand it over to him. Let me know if you need any assistance with the practicalities.
Note that, as haddock now uses it, xhtml is part of a ghc tree in the HEAD. We have a darcs2 repo for it, without the pre-3000.2.0.1 history: http://darcs.haskell.org/packages/xhtml/ Thanks Ian

Ian Lynagh wrote:
On Thu, Jul 29, 2010 at 07:18:23PM +0100, Bjorn Bringert wrote:
Robin Bate Boerop
is the only person to express interest in taking over xhtml. I hereby hand it over to him. Let me know if you need any assistance with the practicalities. Note that, as haddock now uses it, xhtml is part of a ghc tree in the HEAD. We have a darcs2 repo for it, without the pre-3000.2.0.1 history: http://darcs.haskell.org/packages/xhtml/
Why did you fork it? I thought the policy for packages ghc needs is to sync with an upstream? Ganesh =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================

On Mon, Aug 02, 2010 at 05:20:54PM +0100, Sittampalam, Ganesh wrote:
Ian Lynagh wrote:
On Thu, Jul 29, 2010 at 07:18:23PM +0100, Bjorn Bringert wrote:
Robin Bate Boerop
is the only person to express interest in taking over xhtml. I hereby hand it over to him. Let me know if you need any assistance with the practicalities. Note that, as haddock now uses it, xhtml is part of a ghc tree in the HEAD. We have a darcs2 repo for it, without the pre-3000.2.0.1 history: http://darcs.haskell.org/packages/xhtml/
Why did you fork it? I thought the policy for packages ghc needs is to sync with an upstream?
I believe when Simon made the repo he couldn't find an upstream repo. Thanks Ian

On Mon, 2 Aug 2010, Ian Lynagh wrote:
On Mon, Aug 02, 2010 at 05:20:54PM +0100, Sittampalam, Ganesh wrote:
Ian Lynagh wrote:
On Thu, Jul 29, 2010 at 07:18:23PM +0100, Bjorn Bringert wrote:
Robin Bate Boerop
is the only person to express interest in taking over xhtml. I hereby hand it over to him. Let me know if you need any assistance with the practicalities. Note that, as haddock now uses it, xhtml is part of a ghc tree in the HEAD. We have a darcs2 repo for it, without the pre-3000.2.0.1 history: http://darcs.haskell.org/packages/xhtml/
Why did you fork it? I thought the policy for packages ghc needs is to sync with an upstream?
I believe when Simon made the repo he couldn't find an upstream repo.
I guess Robin and you/the GHC team will need to decide which repo to keep going, then. Having both indefinitely would be horrible. Ganesh

On 2 August 2010 17:26, Ganesh Sittampalam
On Mon, 2 Aug 2010, Ian Lynagh wrote:
On Mon, Aug 02, 2010 at 05:20:54PM +0100, Sittampalam, Ganesh wrote:
Ian Lynagh wrote: Why did you fork it? I thought the policy for packages ghc needs is to sync with an upstream? I believe when Simon made the repo he couldn't find an upstream repo. I guess Robin and you/the GHC team will need to decide which repo to keep going, then. Having both indefinitely would be horrible.
It makes sense to have the repo at http://darcs.haskell.org/packages/xhtml/ be the upstream repo, and for GHC to sync with it. I haven't yet looked at the XHTML in GHC HEAD to see whether it is out of sync. If it is not, then that should be corrected, first. Agreed? -- Robin Bate Boerop

Robin Bate Boerop wrote:
On 2 August 2010 17:26, Ganesh Sittampalam
wrote: On Mon, 2 Aug 2010, Ian Lynagh wrote:
On Mon, Aug 02, 2010 at 05:20:54PM +0100, Sittampalam, Ganesh wrote:
Ian Lynagh wrote: Why did you fork it? I thought the policy for packages ghc needs is to sync with an upstream? I believe when Simon made the repo he couldn't find an upstream repo. I guess Robin and you/the GHC team will need to decide which repo to keep going, then. Having both indefinitely would be horrible.
It makes sense to have the repo at http://darcs.haskell.org/packages/xhtml/ be the upstream repo, and for GHC to sync with it. I haven't yet looked at the XHTML in GHC HEAD to see whether it is out of sync. If it is not, then that should be corrected, first.
Agreed?
According to Ian's previous email, GHC now has a completely fresh and incompatible (darcs-2) repo:
Note that, as haddock now uses it, xhtml is part of a ghc tree in the HEAD. We have a darcs2 repo for it, without the pre-3000.2.0.1 history: http://darcs.haskell.org/packages/xhtml/
Ganesh =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/3/10 11:52 , Sittampalam, Ganesh wrote:
Robin Bate Boerop wrote:
It makes sense to have the repo at http://darcs.haskell.org/packages/xhtml/ be the upstream repo, and for GHC to sync with it. I haven't yet looked at the XHTML in GHC HEAD to see whether it is out of sync. If it is not, then that should be corrected, first.
According to Ian's previous email, GHC now has a completely fresh and incompatible (darcs-2) repo:
That's really just an implementation detail, though; the issue isn't whether the repo format is compatible (GHC already has to deal with that for other external packages it uses), but whether the *code* is compatible. - -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxYSPwACgkQIn7hlCsL25XoOACffrKmfsnJkLFClf1vyZJBVdFP OvMAoLRCototDYLjEPyRNqD1Oo/UOBbn =d+mH -----END PGP SIGNATURE-----

On Tue, Aug 03, 2010 at 12:47:44PM -0300, Robin Bate Boerop wrote:
On 2 August 2010 17:26, Ganesh Sittampalam
wrote: On Mon, 2 Aug 2010, Ian Lynagh wrote:
On Mon, Aug 02, 2010 at 05:20:54PM +0100, Sittampalam, Ganesh wrote:
Ian Lynagh wrote: Why did you fork it? I thought the policy for packages ghc needs is to sync with an upstream? I believe when Simon made the repo he couldn't find an upstream repo. I guess Robin and you/the GHC team will need to decide which repo to keep going, then. Having both indefinitely would be horrible.
It makes sense to have the repo at http://darcs.haskell.org/packages/xhtml/ be the upstream repo, and for GHC to sync with it. I haven't yet looked at the XHTML in GHC HEAD to see whether it is out of sync.
GHC uses the http://darcs.haskell.org/packages/* repos for its libraries. In some cases these are the main repo, and in other cases they are periodically synced with an upstream repo. For xhtml, an upstream repo on community probably makes most sense. Thanks Ian
participants (6)
-
Bjorn Bringert
-
Brandon S Allbery KF8NH
-
Ganesh Sittampalam
-
Ian Lynagh
-
Robin Bate Boerop
-
Sittampalam, Ganesh