Hi,
I am looking for reviews for libndn-cxx and I'll review a package in return.
https://bugzilla.redhat.com/show_bug.cgi?id=1255973
Named Data Networking (NDN) is a content based Future Internet
Architecture. This library provides the primitives to develop
applications for NDN.
Thanks!
--
Reg
>> Given the size of the wiki, I am surprised that there is no
>> documentation in this regard.
>> I have started one: https://fedoraproject.org/wiki/Packaging/FAQ
>
> I don't think spreading out the information without any references from
> anywhere else is useful. If this needs to be documented,
> I think, just in case it's not clear, that the typical way this should
> be handled is that on installation the software should not create the
> necessary database; instead the creation process should be documented
> for the user to complete manually. So when the software is packaged,
> there's n
> My understanding was that we never touch databases in RPMs, period. We
> don't create, modify, update, or remove. I can't recall at the moment
> where this stems from, but the rationale, as I recall, was that we can
> never be sure if the database is available at RPM install/upgrade time.
> Plu
On Sat, Jan 8, 2011 at 2:18 PM, Kevin Kofler wrote:
> susmit shannigrahi wrote:
>> For subsequent installations (if tried), it simply overwrites the
>> database. In this process, it asks the user whether to overwrite the
>> DB or not.
>
> And what happens if you say
> Yes but you are better off explaining what the specifically requires user
> interaction and we can potentially suggest good ways of handling it to
> upstream
This software (gnumed-server, which is not yet in bugzilla) uses a
postgres database for storing data.
For subsequent installations (if t
Hi,
Sorry if this has been discussed before, but I can not find much about this.
What is Fedora's policy regarding RPM packaging of software that needs
user interaction during installation? Is it to be patched and made
non-interactive?
Thanks.
--
Regards,
Susmit.
=
