Simply having a git repository does not imply that its source.

In fact, if its considered compiled (minified), I'm thinking the debian rules 
would prevent sourcing from it?

Thanks,
Kevin
________________________________________
From: Donald Stufft [don...@stufft.io]
Sent: Friday, November 21, 2014 8:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Horizon] the future of angularjs development      
in Horizon

> On Nov 21, 2014, at 11:32 AM, Jeremy Stanley <fu...@yuggoth.org> wrote:
>
> On 2014-11-21 07:31:36 -0500 (-0500), Donald Stufft wrote:
>> You can’t. Bower doesn’t have “traditional” packages where you take a
>> directory and archive it using tar/zip/whatever and then upload it to
>> some repo. Bower has a registry which maps names to git URLs and then
>> the bower CLI looks up that mapping, fetches the git repository and then
>> uses that as the input to the “look at metadata and do stuff with files”
>> part of the package manager instead of the output of an un-unarchival
>> command.
>
> This raises interesting free software philosophy/license
> questions... how do I redistribute (or even examine) the "source" of
> a bower-managed package? Is there a way without actually
> reverse-engineering the toolchain?

Well it’s a git repository, so you could just clone it and look at it.

---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to