I'm starting to package more of the X2Go stuff and running into some Debianisms. Namely different source and binary package names. For example:
The source package "x2goplasmabingings" with source tarball x2goplasmabindings-3.0.1.5.tar.gz produces a binary package called "plasma-widget-x2go" (which matches the way other plasma widgets are named).
So, is a package like:
Name: x2goplasmabindings Summary: Plasma widget for control X2go sessions
%description %description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%package -n plasma-widget-x2go Summary: %{summary}
%description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%files -n plasma-widget-x2go -f plasma_applet_x2goplasmoid.lang ...
Okay? Is there a way to avoid repeating the description?
Hi,
This will create two packages, probably not what you want, right ?
Why not simply name the package plasma-widget-x2go ? It only means you can't use %{name} in the Source tag, am I missing something ?
And of course you'd have to tweak your %setup with the right params.
Dridi
On Fri, Sep 6, 2013 at 11:48 PM, Orion Poplawski orion@cora.nwra.com wrote:
I'm starting to package more of the X2Go stuff and running into some Debianisms. Namely different source and binary package names. For example:
The source package "x2goplasmabingings" with source tarball x2goplasmabindings-3.0.1.5.tar.gz produces a binary package called "plasma-widget-x2go" (which matches the way other plasma widgets are named).
So, is a package like:
Name: x2goplasmabindings Summary: Plasma widget for control X2go sessions
%description %description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%package -n plasma-widget-x2go Summary: %{summary}
%description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%files -n plasma-widget-x2go -f plasma_applet_x2goplasmoid.lang ...
Okay? Is there a way to avoid repeating the description?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com -- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
On 09/07/2013 03:28 AM, Dridi Boukelmoune wrote:
Hi,
This will create two packages, probably not what you want, right ?
No, it will only create plasma-widget-x2go because there is no plain "%files" section.
Why not simply name the package plasma-widget-x2go ?
Because the Fedora Naming Guidelines ties naming it to up upstream tarball name or project name. The upstream source tarball and project is x2goplasmabindings. They seem to do this because they have x2gognomebindings, x2golxdebindings, etc. I have yet checked the name of the binary packages produced from them.
It only means you can't use %{name} in the Source tag, am I missing something ?
And of course you'd have to tweak your %setup with the right params.
Dridi
On Fri, Sep 6, 2013 at 11:48 PM, Orion Poplawski orion@cora.nwra.com wrote:
I'm starting to package more of the X2Go stuff and running into some Debianisms. Namely different source and binary package names. For example:
The source package "x2goplasmabingings" with source tarball x2goplasmabindings-3.0.1.5.tar.gz produces a binary package called "plasma-widget-x2go" (which matches the way other plasma widgets are named).
So, is a package like:
Name: x2goplasmabindings Summary: Plasma widget for control X2go sessions
%description %description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%package -n plasma-widget-x2go Summary: %{summary}
%description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%files -n plasma-widget-x2go -f plasma_applet_x2goplasmoid.lang ...
Okay? Is there a way to avoid repeating the description?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com -- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
-- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
Hi,
You can safely ignore the upstream name to keep consistency with other distributions: https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming
Dridi
On Sun, Sep 8, 2013 at 5:48 AM, Orion Poplawski orion@cora.nwra.com wrote:
On 09/07/2013 03:28 AM, Dridi Boukelmoune wrote:
Hi,
This will create two packages, probably not what you want, right ?
No, it will only create plasma-widget-x2go because there is no plain "%files" section.
Why not simply name the package plasma-widget-x2go ?
Because the Fedora Naming Guidelines ties naming it to up upstream tarball name or project name. The upstream source tarball and project is x2goplasmabindings. They seem to do this because they have x2gognomebindings, x2golxdebindings, etc. I have yet checked the name of the binary packages produced from them.
It only means you can't use %{name} in the Source tag, am I missing something ?
And of course you'd have to tweak your %setup with the right params.
Dridi
On Fri, Sep 6, 2013 at 11:48 PM, Orion Poplawski orion@cora.nwra.com wrote:
I'm starting to package more of the X2Go stuff and running into some Debianisms. Namely different source and binary package names. For example:
The source package "x2goplasmabingings" with source tarball x2goplasmabindings-3.0.1.5.tar.gz produces a binary package called "plasma-widget-x2go" (which matches the way other plasma widgets are named).
So, is a package like:
Name: x2goplasmabindings Summary: Plasma widget for control X2go sessions
%description %description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%package -n plasma-widget-x2go Summary: %{summary}
%description -n plasma-widget-x2go X2go is a server-based computing environment with - session resuming - low bandwidth support - LDAP support - client side mass storage mounting support - audio support - authentication by smartcard and USB stick
This package adds a plasma widget (KDE4) for controlling your X2go session.
%files -n plasma-widget-x2go -f plasma_applet_x2goplasmoid.lang ...
Okay? Is there a way to avoid repeating the description?
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com -- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
-- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
-- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
packaging@lists.fedoraproject.org