Re: opensync ports
Gabor Tjong A Hung píše v ne 17. 06. 2007 v 11:49 +0200:
> I am new to porting and have tried to port opensync, and the result is
> included as attachment.
.pc files must go to libdata/pkgconfig, not in lib/pkgconfig.
What's up with pkg-message? It does not seem to be referenced anywhere
in the port.
>- There is a devel/libopensync. I'm not sure if this is the same port.
>It appears to be, but this port is version 0.17. This was released
>04/23/05, so I thought I better start anew.
>
> Should the port be called libopensync? or is opensync the correct name?
It's the same port, do it as an update on that directory.
>- The following lines were also part of the install instructions.
>
> # this is required that frontends and plugins find the opensync-1.0.pc file
> export PKG_CONFIG_PATH=$OPENSYNC_BUILD/lib/pkgconfig:$PKG_CONFIG_PATH
>
> was it correct of me to assume that
> CONFIGURE_ENV= PKG_CONFIG_PATH=${LOCALBASE}/lib/pkgconfig would be
> equivalent?
Have you tried without it? Did it worked? I have a feeling this line
will have zero effect on the build.
>- Based on the pkg-plist I also assumed it had some libraries, so I
>added a USE_LDCONFIG= yes, although I am hesitating if USE_LDCONFIG=
>${PREFIX}/lib/ ${PREFIX}/lib/opensync/formats ${PREFIX}/lib/pkgconfig
>
> it does compile fine *with* and *without* USE_LDCONFIG
It will compile with or without USE_LDCONFIG. USE_LDCONFIG is ment to
expose libraries for other ports. You don't need to expose libraries to
ldconfig, if they are never linked again, only dl_open()ed on runtime.
Typically, this covers all plugins. I'm quite sure the content of
lib/opensync will be dl_open plugins.
lib/pkgconfig does not contain any shared libraries.
>- Library dependencies. Is there a way to *know* what the port depends
>on except from the documentation provided? I couldn't find any dependancies
>in the documentation of opensync. My port does seem to clean
>scons-0.97, python24-2.4.4 and opensync-0.30.
You should read make configure output, it usually checks for
dependencies there. If it uses scons for build instead of make, I think
you might have the dependency list right here.
Clean space test will help you verify this. You could set up Tinderbox
for that.
> Furthermore, since this is not an application, how can I *know" if this port
> is succesfully ported?
Port the application too :)
--
Pav Lucistnik <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Mischief managed.
signature.asc
Description: Toto je digitálně podepsaná část zprávy
opensync ports
Dear all,
I am new to porting and have tried to port opensync, and the result is
included as attachment.
I was however unsure about certain things and I'd like some help before
submitting a PR.
- There is a devel/libopensync. I'm not sure if this is the same port.
It appears to be, but this port is version 0.17. This was released
04/23/05, so I thought I better start anew.
Should the port be called libopensync? or is opensync the correct name?
http://www.opensync.org/wiki/devel-branch-0.30 indicates that version
0.30seems to state that this is a devel version, I am however not so
sure about
how outdated that page is. This is another reason why perhaps it should have
a different name since the 0.3x seems to be a big step from the 0.2x(and
thus bigger than 0.17)
- The following lines were also part of the install instructions.
# this is required that frontends and plugins find the opensync-1.0.pc file
export PKG_CONFIG_PATH=$OPENSYNC_BUILD/lib/pkgconfig:$PKG_CONFIG_PATH
was it correct of me to assume that
CONFIGURE_ENV= PKG_CONFIG_PATH=${LOCALBASE}/lib/pkgconfig would be
equivalent?
- Based on the pkg-plist I also assumed it had some libraries, so I
added a USE_LDCONFIG= yes, although I am hesitating if USE_LDCONFIG=
${PREFIX}/lib/ ${PREFIX}/lib/opensync/formats ${PREFIX}/lib/pkgconfig
it does compile fine *with* and *without* USE_LDCONFIG
- Library dependencies. Is there a way to *know* what the port depends
on except from the documentation provided? I couldn't find any dependancies
in the documentation of opensync. My port does seem to clean
scons-0.97, python24-2.4.4 and opensync-0.30.
Furthermore, since this is not an application, how can I *know" if this port
is succesfully ported?
Regards, Gabor
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file". Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# opensync
# opensync/pkg-descr
# opensync/pkg-plist
# opensync/distinfo
# opensync/Makefile
# opensync/pkg-message
#
echo c - opensync
mkdir -p opensync > /dev/null 2>&1
echo x - opensync/pkg-descr
sed 's/^X//' >opensync/pkg-descr << 'END-of-opensync/pkg-descr'
XOpenSync is a PIM (Personal Information Management) data synchronization
Xframework that consists of several plug-ins that can be used to
Xconnect to different devices and systems. For a list of currently supported
Xdevices see http://www.opensync.org/wiki/DeviceCompatibilityList.
XWWW: http://www.opensync.org/wiki/Evo2-File
END-of-opensync/pkg-descr
echo x - opensync/pkg-plist
sed 's/^X//' >opensync/pkg-plist << 'END-of-opensync/pkg-plist'
Xbin/osplugin
Xbin/osyncbinary
Xbin/osyncdump
Xinclude/opensync-1.0/opensync/archive/opensync_archive.h
Xinclude/opensync-1.0/opensync/data/opensync_change.h
Xinclude/opensync-1.0/opensync/data/opensync_data.h
Xinclude/opensync-1.0/opensync/engine/opensync_engine.h
Xinclude/opensync-1.0/opensync/engine/opensync_obj_engine.h
Xinclude/opensync-1.0/opensync/engine/opensync_status.h
Xinclude/opensync-1.0/opensync/file.h
Xinclude/opensync-1.0/opensync/format/opensync_converter.h
Xinclude/opensync-1.0/opensync/format/opensync_filter.h
Xinclude/opensync-1.0/opensync/format/opensync_format_env.h
Xinclude/opensync-1.0/opensync/format/opensync_objformat.h
Xinclude/opensync-1.0/opensync/format/opensync_time.h
Xinclude/opensync-1.0/opensync/group/opensync_group.h
Xinclude/opensync-1.0/opensync/group/opensync_group_env.h
Xinclude/opensync-1.0/opensync/group/opensync_member.h
Xinclude/opensync-1.0/opensync/helper/opensync_anchor.h
Xinclude/opensync-1.0/opensync/helper/opensync_hashtable.h
Xinclude/opensync-1.0/opensync/ipc/opensync_message.h
Xinclude/opensync-1.0/opensync/ipc/opensync_queue.h
Xinclude/opensync-1.0/opensync/ipc/opensync_serializer.h
Xinclude/opensync-1.0/opensync/mapping/opensync_mapping.h
Xinclude/opensync-1.0/opensync/mapping/opensync_mapping_entry.h
Xinclude/opensync-1.0/opensync/mapping/opensync_mapping_table.h
Xinclude/opensync-1.0/opensync/mapping/opensync_mapping_view.h
Xinclude/opensync-1.0/opensync/merger/opensync_capabilities.h
Xinclude/opensync-1.0/opensync/merger/opensync_capability.h
Xinclude/opensync-1.0/opensync/merger/opensync_merger.h
Xinclude/opensync-1.0/opensync/merger/opensync_xmlfield.h
Xinclude/opensync-1.0/opensync/merger/opensync_xmlfieldlist.h
Xinclude/opensync-1.0/opensync/merger/opensync_xmlformat.h
Xinclude/opensync-1.0/opensync/opensync-client.h
Xinclude/opensync-1.0/opensync/opensync-context.h
Xinclude/opensync-1.0/opensync/opensync-data.h
Xinclude/opensync-1.0/opensync/opensync-engine.h
Xinclude/opensync-1.0/opensync/opensync-error.h
Xinclude/opensync-1.0/opensync/opensync-format.h
Xinclude/opensync-1.0/opensync/opensync-group.h
Xinclude/opensync-1.0/opensync/opensync-helper.h
Xinclude/opensync-1.0/opensync/opensync-ipc.h
Xinclude/opensync-1.0
