Actually it's not as bad as I thought. We'd have duplicate entries;
the original would now have the project-part and '/' in explicitly in
each part name; and the new would be a copy with the slashes changed
to '-'. This will allow older versions of snapcraft to continue to
use the versions with '
El 10/08/16 a las 03:14, Didier Roche escribió:
> Le 09/08/2016 à 23:41, Joe Talbott a écrit :
> Namespacing was really nice for things like desktop/ parts
> (desktop/gtk3, desktop/gtk2, desktop/qt5, desktop/qt4,
> desktop/glibonly). There is as well mqtt-paho/python2 and
> pqtt-patho/python3.
I
On Wed, Aug 10, 2016 at 8:29 AM, Didier Roche wrote:
> Le 10/08/2016 à 13:51, Joe Talbott a écrit :
>
>>
>> The plan would be to convert the wiki parts and their origins but to
>> have a deprecation warning for any snapcraft.yaml using the namespaced
>> part names and to have snapcraft automatical
Le 10/08/2016 à 13:51, Joe Talbott a écrit :
>
> The plan would be to convert the wiki parts and their origins but to
> have a deprecation warning for any snapcraft.yaml using the namespaced
> part names and to have snapcraft automatically convert '/' to '-' during
> part loading. This should le
On Aug 10, 2016 2:15 AM, "Didier Roche" wrote:
>
> Le 09/08/2016 à 23:41, Joe Talbott a écrit :
> > Dear Snapcrafters,
>
> Hey Joe,
> >
> > The wiki introduced the concept of sub-parts and used namespacing to
> > associate a list of sub-parts with a project-part. However the
> > concept was ill-c
Le 09/08/2016 à 23:41, Joe Talbott a écrit :
> Dear Snapcrafters,
Hey Joe,
>
> The wiki introduced the concept of sub-parts and used namespacing to
> associate a list of sub-parts with a project-part. However the
> concept was ill-conceived and now needs to be removed. In essence,
> all parts sh
Dear Snapcrafters,
The wiki introduced the concept of sub-parts and used namespacing to
associate a list of sub-parts with a project-part. However the
concept was ill-conceived and now needs to be removed. In essence,
all parts should be top level parts. Each entry in the wiki should
identify o
