I'd be happy to hear what the problem was. I'm still packaging metalink
but it required a new upstream release because some source files where
missing their license, so the packaging was dropped dead till a new
release is made (which I still have not found the time for).

Currently I'm also reading up on Python packaging and I hope the
packaging of libmetalink is still going forward, because then I can get
metalink to depend on that in the new version.

For all the packages I havn't been able to get into Ubuntu yet, I'll be
publishing preliminary work on packages in my personal packaging
archive:
 https://launchpad.net/~bneijt/+archive

Any comments, requests etc. are welcome.

Bram

On Thu, 2008-11-27 at 00:06 -0500, Anthony Bryan wrote:
> On Wed, Nov 26, 2008 at 8:53 PM, Nicolas Alvarez
> <[EMAIL PROTECTED]> wrote:
> >
> > Anthony Bryan wrote:
> >> # I couldn't get any of the metalink
> >> # generators to work, so this was born.
> >
> > That is definitely a problem we should address... Thomas saw none of the
> > generators worked, and wrote his own. But other people could give up with
> > metalinks if they can't use the generators.
> 
> good point, glad you brought it up!
> 
> I contacted him to try & find out if they really didn't work, or if
> this was due to documentation, or bad marketing (the website should
> have something really simple to explain this).
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Metalink Discussion" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/metalink-discussion?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to