On Thu, Oct 18, 2018 at 2:10 PM Zolee K <zoleelikesdeb...@gmail.com> wrote:
>
> Hehttp://cgit.openembedded.org/meta-openembedded/tree/meta-networking/recipes-daemons/proftpd/proftpd_1.3.6.bb?h=master#n99llo,
>
> I'm very new to the Yocto Project and I got a Barix module that is to be 
> developped with Yocto.
> I managed to insert the desired programs into the linux image (nano, rsync, 
> mc, proftpd, vlc) by modifying a recipe file but now I'd like to make some 
> changes. I thought I would start with modifying the proftpd.conf file.
>
> As I read the manuals it is clear to me that the best way to do this to make 
> .append files.
>
> I created my own proftpd.conf file, modified it a bit, example I only renamed 
> the default server name. After that I modified the bb recipe file's sources 
> section this way:
>
> SRC_URI = "ftp://ftp.proftpd.org/distrib/source/${BPN}-${PV}.tar.gz \
> file://proftpd.conf \
> file://basic.conf.patch \
> file://proftpd-basic.init \
> file://default \
> file://close-RequireValidShell-check.patch \
> file://contrib.patch \
> file://build_fixup.patch \
> file://proftpd.service \
> "
> The red one is a new file among the other patch files however my slight 
> changes will not bitbake. The proftpd is going to be in the image, but with a 
> its default proftpd.conf file. It looks like my config file never gets 
> inserted in the target.
>
> Could you please help me out how should I start with this proftpd 
> customisation?
>

so you can have sed ops to do the needed tweaks in existing conf flile
in the bbappend e.g.
do_install_append () {

sed .....
}

see here

http://cgit.openembedded.org/meta-openembedded/tree/meta-networking/recipes-daemons/proftpd/proftpd_1.3.6.bb?h=master#n99



> Thanks,
>
> Zoli
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to