Re: bootstrapping a new horde library pear xml

Am 30.03.2018 um 11:15 schrieb Ralf Lang:
>
> Am 16.02.2018 um 14:58 schrieb Jan Schneider:
>>
>> I think the best approach would be to introduce a "horde-components
>> init" command that creates all necessary files for a
>> library/application to be manageable through horde-components.
>>
>> As for your original question: .horde.yml and changelog.yml should in
>> the long term be the master information files which generate all other
>> files. Anything else should be considered a bug.
>>
> I agree we need a new command. I have set up a scenario in a clean
> developer container and for now, it seems to work if I provide
> rudimentary .horde.yml, package.xml, doc/CHANGES, doc/changelog.yml.
> The actual content of the xml does not matter as long as it is
> well-formed and has all required sections. I will try to strip down as
> much as possible, then build such an init function.

The easter bunny just hid a little easter egg on github ;-)
https://github.com/horde/components/pull/1

-- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: [email protected]
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]