Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Why opensuse use explicit distro name in a REPO path

  1. #1

    Default Why opensuse use explicit distro name in a REPO path

    Subject. Why just not use something like <repo_base_path><$version>
    There $version can be taken from /etc/issue or other special place. it remove redundance, make distro upgrade easier. Now opensuse dist upgrade so primitive.. just remove all old repos.

  2. #2

    Default Re: Why opensuse use explicit distro name in a REPO path

    Quote Originally Posted by slimy View Post
    Subject. Why just not use something like <repo_base_path><$version>
    And what's the difference to <repo_base_path>/openSUSE_<$version> as it is now?
    And the standard repos already have a path as you propose:
    http://download.opensuse.org/distribution/13.1/ f.e.

    Btw, there's also openSUSE-current which always points to the latest version, i.e. 13.1 ATM.
    This won't help you with OBS repos though.

    But as mentioned in SDB:System upgrade - openSUSE, just run "sed -i 's/12\.3/13\.1/g' /etc/zypp/repos.d/*" and all your repos will be changed to the new openSUSE version (you have to adapt the version numbers accordingly of course).
    Just changing the repo path wouldn't make that automatic either, and it's not necessary to implement the thing I think you have in mind (automatic distro upgrade).

  3. #3
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Why opensuse use explicit distro name in a REPO path

    On 2013-12-05 09:36, slimy wrote:
    >
    > Subject. Why just not use something like <repo_base_path><$version>
    > There $version can be taken from /etc/issue or other special place. it
    > remove redundance, make distro upgrade easier. Now opensuse dist upgrade
    > so primitive.. just remove all old repos.


    Precisely to impede automatic distro upgrade.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

  4. #4

    Default Re: Why opensuse use explicit distro name in a REPO path

    Quote Originally Posted by wolfi323 View Post
    And the standard repos already have a path as you propose:
    http://download.opensuse.org/distribution/13.1/ f.e.

    Btw, there's also openSUSE-current which always points to the latest version, i.e. 13.1 ATM.
    This won't help you with OBS repos though.

    But as mentioned in SDB:System upgrade - openSUSE, just run "sed -i 's/12\.3/13\.1/g' /etc/zypp/repos.d/*" and all your repos will be changed to the new openSUSE version (you have to adapt the version numbers accordingly of course).
    Just changing the repo path wouldn't make that automatic either, and it's not necessary to implement the thing I think you have in mind (automatic distro upgrade).
    Еexactly what I'm taking about. You have to use regexp for upgrage, which have no any warranty. Easy find that regexp mach something but much harder that not much something in wrong place.
    Preventing to autoupgrade? I see no problem with that. If distro name contain in /etc/issue while you not change what no changing for distros.
    And what's the difference to <repo_base_path>/openSUSE_<$version> as it is now?
    Yes path quite the same. But I mean use only repo_base_path other parts could inserts in the path by zypper. This is just SW development usual practice DRY. Use name constant with common value instead place value in each place.

  5. #5

    Default Re: Why opensuse use explicit distro name in a REPO path

    Quote Originally Posted by slimy View Post
    Еexactly what I'm taking about. You have to use regexp for upgrage, which have no any warranty. Easy find that regexp mach something but much harder that not much something in wrong place.
    Preventing to autoupgrade? I see no problem with that. If distro name contain in /etc/issue while you not change what no changing for distros.

    Yes path quite the same. But I mean use only repo_base_path other parts could inserts in the path by zypper. This is just SW development usual practice DRY. Use name constant with common value instead place value in each place.
    And what if you _don't_ want to upgrade immediately when a new version is released? I.e. because the current one is still supported for 10 months, or maybe you are using Evergreen, which is still supported even longer?

    But your suggestion doesn't work anyway, since /etc/issue contains the _current_ version, not the next.
    And /etc/issue is for displaying the greeting text in text mode, if you want to propose something like that, suggest "lsb-release -rs"...
    But even then you still have the problem, that you don't know when the next version is available and which version number it will have. So your proposal wouldn't really change anything.
    And as I said, there's already openSUSE-current, which goes into the direction you want to go, just use that and you'll always have the repos of the latest openSUSE version.

  6. #6

    Default Re: Why opensuse use explicit distro name in a REPO path

    Quote Originally Posted by wolfi323 View Post
    And what if you _don't_ want to upgrade immediately when a new version is released? I.e. because the current one is still supported for 10 months, or maybe you are using Evergreen, which is still supported even longer?

    But your suggestion doesn't work anyway, since /etc/issue contains the _current_ version, not the next.
    And /etc/issue is for displaying the greeting text in text mode, if you want to propose something like that, suggest "lsb-release -rs"...
    But even then you still have the problem, that you don't know when the next version is available and which version number it will have. So your proposal wouldn't really change anything.
    And as I said, there's already openSUSE-current, which goes into the direction you want to go, just use that and you'll always have the repos of the latest openSUSE version.
    Where is the problem with upgrade?If your constant with distro version still the same. I do not suggest use "current". And doesn't matter really /etc/issue or lsb-release I mean these as example. Better change one string then do the same action for each, even with regexp no warranty from errors.
    My point is if zypper by itself knows 'it distro version' why we still MUST use the same constants explicit in the path?

  7. #7

    Default Re: Why opensuse use explicit distro name in a REPO path

    Quote Originally Posted by slimy View Post
    Where is the problem with upgrade?If your constant with distro version still the same. I do not suggest use "current". And doesn't matter really /etc/issue or lsb-release I mean these as example. Better change one string then do the same action for each, even with regexp no warranty from errors.
    My point is if zypper by itself knows 'it distro version' why we still MUST use the same constants explicit in the path?
    And why change it then?

    A repo can have an arbitrary URL, there's no guarantee that it ends in $version. So how should this work for non-official repos? Or local directories on your harddisk added as repo? Or the installation medium?

    And how should an online distribution upgrade work then? Or a Factory installation?

    Anyway, that discussion is moot here. Open a feature request at http://features.opensuse.org/ if you really want to have this implemented.

  8. #8
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Why opensuse use explicit distro name in a REPO path

    On 2013-12-05 13:46, slimy wrote:
    > My point is if zypper by itself knows 'it distro version' why we still
    > MUST use the same constants explicit in the path?


    No, it does not.

    We use them to avoid unintentionally upgrading a package to one of a
    different version. Currently there are repos active for 11.4, 12.2,
    12.3, and 13.1, all supported. How do you know which is which if all
    have the same path?

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

  9. #9

    Default Re: Why opensuse use explicit distro name in a REPO path

    Quote Originally Posted by robin_listas View Post
    On 2013-12-05 13:46, slimy wrote:
    > My point is if zypper by itself knows 'it distro version' why we still
    > MUST use the same constants explicit in the path?


    No, it does not.

    We use them to avoid unintentionally upgrading a package to one of a
    different version. Currently there are repos active for 11.4, 12.2,
    12.3, and 13.1, all supported. How do you know which is which if all
    have the same path?

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)
    Took that information from a file. You are seems misunderstood me, I agree about path on repo server, but I talk about something like that on distro side not a server
    PHP Code:
    $VERSION 'opensuse13.1' // took from /etc/issue or from lsb-release or maybe other special file

    http::/<repo1_root_path/$VERSION
    http
    ::/<repo2_root_path/$VERSION
      
    ....
    http::/<repoN_root_path/$VERSION 

  10. #10
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Why opensuse use explicit distro name in a REPO path

    On 2013-12-06 15:06, slimy wrote:

    > Took that information from a file. You are seems misunderstood me, I
    > agree about path on repo server, but I talk about something like that on
    > distro side not a server
    >
    > PHP code:
    > --------------------
    > $VERSION = 'opensuse13.1' // took from /etc/issue or from lsb-release or maybe other special file
    >
    > http::/<repo1_root_path/$VERSION
    > http::/<repo2_root_path/$VERSION
    > ....
    > http::/<repoN_root_path/$VERSION
    > --------------------


    IMO, that's complicating things.

    Side note: Please use code tags, not PHP tags. The '#' button on the editor.


    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •